Imagine someone opening a pull request with that — it would never pass a code review!
695 karma · joined October 29, 2012
Imagine someone opening a pull request with that — it would never pass a code review!
And in order for that symbol to exist (be expressed / thought of / conceived), it must be a part of some other existing universe that allows that...
One thing is some random payment processor API that you encounter only once in your career (it doesn't need to be terse and it is better to avoid any magic here) — and whole another thing is stuff like jQuery or React, which I can produce/read in thousands of lines per day. You would design such APIs with different objectives, like being easy to type, easy to read (once you know the API).
The mantra "explicit is better than implicit" is wrong, because it really depends.
It might be that Iran doesn't want to cause any real damage (as then Israel would destroy its oil industry and nuclear sites in retaliation) — it only wants to save face. For that, a media picture of "hundreds of missiles falling on Israel" would perfectly suffice — they can sell it domestically. Just bomb some bushes and deserts and call it a day.
Another idea is not to set an arbitrary fixed price, but to auction green cards off, with a limited annual cap. So the market would decide the price (the highest bidder wins).
To me true AGI is achieved when it gets agency, becomes truly autonomous and could do real things best of us, humans, do — start and run successful businesses, contribute to science, to culture, to politics. It still could follow human "prompts" and be aligned to some set of objectives, but it would act autonomously, using every available interface to the human realm to achieve them.
And it absolutely does not matter if it "uses the same principles as human brain" or not. Could be dumb matrix multiplications and "next token prediction" all the way down.
Not true. In TypeScript, there are tuples — you can perfectly describe an array having 2 elements with different types, and even give names to them:
type KVPairTuple = [key: string, value: number]
We use it all the time for simple 2-element thingies. You can say JavaScript isn't TypeScript, but cmon, just everybody out there uses TypeScript, it is the basic norm nowadays. So we're really talking about TypeScript semantics here.Also, even JS uses tuples for its core APIs. Enter `Object.entries` and `Object.fromEntries` — they operate on kv-pairs in form of 2-element arrays. So your assertion that tuples are something alien to JS ecosystem isn't accurate simply because of that.
We have a rule of thumb in our projects: if you use useEffect directly in application code, it is a probable sign that something is wrong with your code, like you're working on a wrong level of abstraction. Almost every direct use of useEffect is better solved with some standard hook from a popular library (like react-use or whatever you like — there are plenty of them).
Like, binding event listeners? useEventListener
Network/async calls? useAsync
timeouts/intervals? useInterval, useTimeout
And etc. etc.
useEffect is really a low-level building block for library code and we rarely use it directly, as it is unsafe and hides the original intent. Much like `new` and `delete` in C++ — you don't use it directly, there are smart pointers. Library hooks are your safe smart pointers over useEffect.
The explanation is actually very simple: because in 100% of times you need to give those two fields custom names. It is easier and more concise with tuple:
const [text, setText] = ...
Than with object + renaming, which quickly gets clumsy when you have dozens of such lines in your component: const {value: text, setValue: setText} = ...Honestly, people used to say the same thing about Bluetooth hands-free devices years ago, and now no one even bats an eye when someone talks using AirPods.
This will surely affect how we speak. It's possible that human language evolution could come to a halt, stuck in time as AI datasets stop being updated.
In the worst case, we will see a global "model collapse" with human languages devolving along with AI's, if future AIs are trained on their own outputs...
If a house and 401k also counted towards net worth, it could impact quite a few Americans. Besides, those who expatriate for tax optimization purposes usually have a significant amount of wealth.
Haven't you heard of exit tax? If you renounce citizenship (or surrender your 8+ year green card), you must pay 30% of your worldwide assets' value (as if you sold it for cash) to the IRS. And if you own something illiquid, you're deep in trouble!
So no, people can't renounce their U.S. citizenship easily, the IRS has accounted for that...
Management probably thinks they don't need the best people anymore, as mediocre employees + ChatGPT (or whatever they use at Amazon) will suffice.
"LLMs are simply predicting next token, it is not thinking/reasoning/etc."
"LLMs can't reason, only humans can reason"
"We will never get to AGI using LLMs"
It's interesting that I don't see much of that sentiment in this post. So, maybe LLMs can reason after all? :)
This means they now need to crank out a working product as quickly as possible, and that means hiring only seasoned seniors with an impressive track record.
Previously, they could have gotten away with having no product at all (all while hiring as no tomorrow, just to pump up their valuation). But those days are gone with the low interest rates.
Can confirm. I nowadays receive mostly messages from people who are looking for a job and curious if our team is hiring. Though it is mostly entry-level candidates (fresh grads, people who have completed bootcamps, etc.), which probably tells something about the job market.
HRs occasionally reach out to me but only to try to sell devs. So it looks like nobody's hiring and everyone is desperately looking for a job. Or maybe it's just LinkedIn is dead and people use other channels to find opportunities.
I personally think re-learning into construction / architecture as a backup plan. IMO we are all living in overly costly and ugly houses, so maybe it could be improved at least a bit :)
True, but you don't need everything at max resolution simultaneously, so you can update your caches according to the current zoom level and thus get infinite zooming if you want.
At a large zoom level, few things get into the viewport, so it shouldn't cause troubles. My guess is that the troublesome scenario is when you zoom out (so that lots of pages can get rendered simultaneously), not when you zoom in?
My point is that while people may want to pursue what you described (some advanced UI behaviors), in practice they fuck up even basic functionality, because even that is almost impossibly hard to implement with text rendering and editing.
For example, in Repaint some basic emojis don't work. And I didn't even try inputting some Arabic or Hebrew or Chinese — I am sure that doesn't work too. Hats off if they manage to do it, but at this point they have spent all their funding on a custom text editor, while they could have spent in on actual features.
I, as a customer, don't care if a product uses WebGL or is written in Rust... All I care if it works or not.
Not entirely true — on Mac I can pinch zoom this Hackernews page super smoothly (in Chrome) using trackpad.
Does it really need WebGL? You could pre-render things to images (memoize your rendering basically) and update the cached images only when the editing happens. As the interactive editing usually happens only locally, it could probably work well.
The obvious upside is that you don't need then to re-invent the browser's renderer and text editing from scratch, you could re-use it.
For example, this stroke me as an extreme NIH:
> We also can’t use the browser’s built-in text editor, so we made one ourselves
People usually just hate custom non-system text inputs, because it is very hard to reproduce the native look and feel of text selection, editing and stuff, and even if you manage to get close to it, there will always be some "uncanny valley" effect...
1. "Smack my bitch up" https://www.youtube.com/watch?v=eU5Dn-WaElI
2. "Voodoo people" https://www.youtube.com/watch?v=6ZYLp5uX9Yw
Those pieces sound exactly the same as the original, but it does not violate copyright because they've been produced by hand. Mind blowing!
I often need to wait for many days for a SWIFT to get through. There are fees — sometimes way larger than crypto fees. Transactions are frequently blocked, and I end up spending a lot of time convincing my bank that the transfer is legitimate.
Plus, they tell you that if there's an error, like sending money to the wrong account, it can't be reversed — just like with crypto. So really, what's the point of all that extra hassle?
As the world becomes more fragmented, with financial and cyber spaces becoming increasingly isolated, crypto is often the only tool left to maintain personal financial freedom.
So, in the long run, I believe crypto will be just fine. The trend isn't likely to reverse anytime soon.