skysight-inc/HackerNews huggingface dataset:
This is a heavily outdated opinion. The "default" react experience nowadays is Next.js and that is definitely a framework not a library.
I have 20 years of experience and thought the article was a pretty good summary of LLM tools and techniques for programming. While it is admittedly pretty high-level, I don't expect an article in Nature to go much deeper on any topic, let alone software development.

And it definitely doesn't have "OpenAI Voice". This was a less formal, less pedagogical style than ChatGPT tends to generate.
Weird sensationalized title to just show an alternative.

I expected a blog post comparing both tools.
Vision Pro does foveated rendering, it was called out as an underlying feature of the platform
Agree heavily with the article. As an app developer, I actively spend my time walking away from frameworks/languages/libraries that start mashing the server weirdly into client code. Each to their own but I think quasi-RPC implementations are a relic of the past.

Treating the network layer as an explicit abstraction to components just feels a better developer experience in the long run. The data abstractions are easier to reason about, and caching albeit always hard, is a lot easier to think about.

I don't even know _why_ React/Next is pushing Server Components. (Part of me wants to join the conspiratorial bandwagon like the author)
Things I notice being “intelligent” (when young people assume that means knowing everything and doing things perfectly the first time)

- the first solution is nearly always wrong (incomplete, reveals problem was not well understood)

- the second solution better addresses the problem, yet isn’t quite right (rough edges)

- the third solution is most often complete in form and function

Also when confronted with a spontaneous problem, unless reflexes will save one’s life, taking three deep breaths before responding most often produces the most level headed recourse.
When you see people write articles about copilot like this, it’s clear they haven’t understood how it works, specifically that it is not a “one shot” generator like chatgpt, and uses other files in your project as part of the prompt [1].

If you’re getting inconsistent results, it’s most likely you’re doing experiments in a single project, and opening a “new file” expecting it to be a “clean slate” like a “new chat” in chat gpt.

…but codex doesn’t work that way.

If you find it “suddenly” figures out how to do something, particularly something you’ve done before, it’s most likely your solution is being fed in as part of the prompt, not that you’ve figured out some magical prompting keywords. Copilot just isn’t that good at code gen.

Personally I’ve found that codex is very predictable in terms of performance and consistency, but, broadly speaking, an order of magnitude less capable than chatgpt.

[1] - https://thakkarparth007.github.io/copilot-explorer/posts/cop...
Honest sales ad: data modelling automation
Thank You. Sorry about not adding to the discussion.
For those saying Jeffrey Perkel has "no programming experience," please see: https://scholar.google.co.uk/scholar?as_q=&btnG=Search+Schol...
There are multiple apps in the App Store that do this. I spent last year implementing pose detection in an exercise app and we used both Apple’s pose detection and a 3rd party’s. The pose (each point of the human form) itself was sent to a machine learning backend at around 30 fps, analyzed, and data returned at about the same speed using gRPC. Each exercise had a set of specific feedback for both positioning (“Stand facing the camera with you arms at your side/Stand sideways to the camera/etc”) and form correction (“Raise your right arm higher above your head etc”). Feedback was spoken out loud to the user and there was a relatively complex set of rules governing which feedback got priority and how often feedback was spoken. I also implemented an on-screen “skeleton” of the user’s human form points that rendered on top of the camera view. Pretty fun project from a tech point of view.
Not being able to profit from "internet money" was probably a good thing. Remember the South Park episode where the Numa Numa guy together with among others Canada demanded the UN giving them their internet money?

That episode is hillarously outdated.
> Hydrogen may be generated by renewable sources such as solar energy, making it overall a cleaner alternative than batteries on a well to wheel basis

Err, what? I guess you could contrive a scenario in which the extra solar panels and equipment needed for generating, managing and storing the hydrogen was less "well" than the batteries for equivalent "wheel" output. Perhaps if you make infrequent but long journeys, so you need a big battery, but only a small amount of power generation, but hydrogen is a very inefficient way of storing electrical power, maybe 50% of the energy back compared to over 90% with batteries.
This is what's concerning. A team that just spent years creating revolutionary hardware that is leaps and bounds ahead of the competition, who by far have the most context to come up with a killer app, could not come up with one. The best they could offer is reading articles in safari an enhancing the viewing experience of movies/shows/live sports.

They should be bursting at the seams with out of this world ideas that this amazing hardware could support. And yet, nothing.
Nope, but I can see why you'd expect that because the actual design is very clever and so it's not obvious how this could work.

What's inside the cheapest authenticators isn't a private key, after all they present a unique random public key for every single enrolment, so that couldn't work if they held a single private key. Instead it's a symmetric key (e.g. AES-256). Lets see how that's done:

When you enrol at a site, the authenticator mints a completely random new public/private key pair (with Elliptic curve crypto it's really easy to pick random key pairs because with a few bit ops any random bits become a random key) and after signing the enrolment step, the authenticator encrypts its new private key using that secret symmetric key and the DNS name in an authenticated encryption mode and provides that encrypted value too.

The browser, with the authenticator's help, puts together the final enrolment document, with a signature and it includes that encrypted private key as a Unique Identifier. All the Unique Identifiers in the protocol are huge random looking numbers, so the encrypted key blends right in with that.

For a web site, you need to store the public key (obviously) and this unique unique identifier value. You have to do that for everybody, anyway, it's mandatory. You can't decrypt the identifier even if you were sure it's encrypted, you don't know the key, so all you can do is play it back when you want a user to authenticate.

When it's played back, the authenticator takes the web site's DNS name, plus its own secret key, and decrypts the identifier to get back its private key, which it can now use to sign authentication messages. Of course if the DNS name is wrong, the decryption fails, which is exactly the same thing as happens if you try to use the wrong authenticator, or you're being phished, or a dozen other things - the authentication can't succeed.
You can be both
> People don't know what they want until you show it to them

You won’t know what people want or how to build it if you don’t _look at what they actually do_ first. There’s no other way of doing it, even Steve Jobs did it this way.

It sounds like a contradiction, but I don’t think it is. He’s talking about people’s biases about new products. Understanding people’s biases is part of watching what they do, as opposed to just considering what they say. He doesn’t say you’re supposed to come up with what people want out of thin air.
Okay.

How is that different from a password? How can you know that when you type your password into a random coffee shop public computer that the computer isn't running a keylogger and sending your credentials to criminals?
The Feb 1986 issue linked in the article caught my attention, since it is the month I was born.

Page 10 starts with a story of someone planning to build a case for the Apple I, to take it to a computer show. The guy called Steve Jobs, and Jobs offered him to send the new tape interface, which Wozniak just finished. It is an utterly amazing read!

https://archive.org/details/computer-shopper-february-1986/C...
Fungal Carbon Sinks
McLuhan famously has this notion of cold and hot media. In the movie theater light shines at a screen and you see its reflection; on TV, and more so with phones, the light beams directly into your eyes. It makes a difference.
Do ads even work on devs?
While there is much talk of protest, nobody in a position of power (like those organizing protests in various subreddits) seems to be offering a diaspora option. The protests are extremely time boxed too, so if I were Reddit, it seems like a fair trade. Very short term harm followed by getting exactly what they want.

I don't see why the protests would have any meaningful impact on Reddit policy. Look at how pointless Occupy Wall Street was, and now imagine they started out by saying they'd only camp there for a weekend.
This is cool -- I like not having to learn jq's bespoke syntax for finding and filtering. But, at a glance it looks like it just shells out to whatever Node.js it finds, so it's not exactly portable or self-contained.

What I really want is a version of this type of tool that's truly a single binary, that implements JSONPath, or some spec'd alternative that I can invest in learning, knowing it's not just a fad.
I keep reading pricepoint is high. it has a M2 and 4k screens... many people spend that much for those.
> In the timeless words of George W Bush Junior "Fool me once shame on you, fool me twice... Wait, I can't be fooled again!"

I agree with your comment, but I can't let such an eloquent presidential quotation be so misquoted.

Bush said, "Fool me once, shame on – shame on you. You fooled me, [I] can't get fooled again."
> Trust but verify...

Based on my own attempts to have ChatGPT generate code for me, it's better to NOT trust it. It tends to hilucinate even with simple requirements.
Apples vs oranges.

`jq` is a CLI processor for JSON (you can filter values etc), while `fx` is a JSON viewer (with some `reducers` functionality).
Future of American dream when 70% of the population cannot afford rent let alone owning.
It seems like there's a US government mandate to kill crypto in the US. This energy would've been better at the time of peak-ICO, directed at the worst offenders.

Going forward I would hope to see the SEC put more of its energy toward people who did ICOs involving untrue statements and legal violations as key parts of their pitches, as well as people who did SPACs with egregious forward projections.
We use AWS, DO and Cloudflare mostly. Self managed I guess
Metabunk Coverage of UFO Whistleblower
The Russia example there is a genuine example of de-dollarisation though, showing why exports matter.
I feel like the animated gif does a great job explaining how it works. If you're at all familiar with jq, it's immediately obvious what this tool does.
But the existing system (involving courts) was determined by individuals who were rather directly voted on by the citizens.

This system of out-of-jail-free cards was decided by a separate group of individuals. If the elected representatives wanted police & friends to be above the law they could've done so and in fact for police they often have (Sovereign Immunity / Qualified Immunity) but for friends they didn't.
Notifications and health tracking
Condoms are cheap
A good overview but a bit short on details. Some crucial things that got omitted (and are generally valid across Central Europe - no idea about the US, India and other places notorious for railway accidents):

- signals, both "old" mechanical and modern filament/LED light based, are continuously monitored for their status. If a wire breaks (for mechanical signals) or the current is abnormal, a fault is detected by the interlock control and there are rigid procedures on how to operate safely under such conditions.

- Signals have some sort of direct connection to a railside element communicating the status of the signal (go/slow/stop) to the locomotive. In the case of the most common used system PZB [1], it's a box containing a tuned inductor circuit, with the resonance frequency changing according to the status of the signal by connecting or disconnecting a capacitor (which can also be done by a mechanical signal). The train drives over these boxes and the locomotive's antenna detects driving over a tuned or mistuned box. The French use a system applying a low voltage to a third, short center rail that gets picked up by a brush [2] or, for high-speed rails, a low-frequency FM carrier signal transmitted over the rails [3].

- railway sections are sub-divided into "blocks", spaced at least a full brake distance from full speed apart. Signals signal to conductors what to do, and axle counters or DC monitors verify a block of rail is free of trains. The purpose of all that effort is to make sure that a) even in the worst case of a conductor missing a red light at full speed, the safety system has enough time to stop the train before it crashes into the train ahead and b) should a train separate and someone made an error in linking the central brake pipe (leading to the front part not braking automatically), the axle counter will detect that less axles came out of the block than came into it. It has the obvious disadvantage that a lot of capacity is wasted by the requirement to have one entirely empty block between trains; as a consequence systems like ETCS or LZB got developed that monitor position, speed and condition of trains and provide a virtual "moving block" leading to better utilization. In the long term, ETCS will lead to a complete elimination of track-side signals and eventually pave the way towards fully automated driving - but that's many decades away.

[1] https://en.wikipedia.org/wiki/Punktf%C3%B6rmige_Zugbeeinflus...

[2] https://en.wikipedia.org/wiki/Crocodile_(train_protection_sy...

[3] https://de.wikipedia.org/wiki/Transmission_Voie-Machine
Password managers did not invent this idea, but we can observe people consistently reusing passwords when they don't have a password manager. It is just undeniable at this point that users cannot be expected to consistently create strong and unique passwords for each service.
Yes. I'm definitely old school and it's a great language if you don't want to use frameworks or other cruft, basically powerful. It's very portable, stable, and fun to work with.
Video describing the engine:

https://www.youtube.com/watch?v=0e785YnDmq0
HN could easily be run as a classic forum. The VC money just makes it possible to have one (?) FTE which makes it alot simpler to not mess up concessions when admins get tired. But ye it is suprising that Ycomb don't want to mess it up. Someone somewhere has good judgement against short term profits for long term?
The product may be good, but I am talking about its price, and how it sold like hot cakes anyway. Consumer goods don't sell as much without marketing, which influencers / celebs provide for free to Apple.
React has already through massive changes with emphasizing classes -> function components -> hooks.

OTOH it hasn't broken backwards compatibility.

I think Server Components are similar to the introduction of hooks because while they require changes to use, they don't affect anything if you aren't using them.

You could argue that it's such a massive change they should make it as a separate framework, but React's approach of adding new approaches but maintaining compatibility seems to have been fairly popular.

Maybe server side rendering isn't what everyone wants to do, but you don't have to. I think we can all agree that if they were FORCING everyone to change what they're doing and use server components it would be more of a problem?
It's an iOS derivative.
There is something here I think. The lisp/C example is useful in that there are things which C lets you express things that lisp usually does not. Garbage collectors for lisp tend to be written in C, even when the lisp in question can directly munge the machine code if you wish. For that matter whether C is useful sugar or obstructive depends strongly on what you want the machine code to be.

It's tempting to handwave away compile time detection of missing cases in pattern matching as nice but inessential. However it is something which gets leaned on very heavily where it is available. It takes a collection of failure modes out of the mind of the programmer to encourage thinking about other things.

Expressive power is probably inconsistent as a concept. Whether introducing a constraint or removing it increases expressivity depends on what one is trying to express. For example, should code that does not typecheck prevent running code which does? Depends on context - it's deeply annoying during development, but helpful to avoid checking in code which no longer works on the paths you weren't looking at.
Good old Kevin Rose is an NFT peddler now!
> Tracking you via your email address is actually better than using cookies (for the advertiser) because it works cross-device and cross-browser.

At least in the EU, you'll need express consent to do this.
The destruction of the Nova Kakhovka dam by Russians follows almost exactly all the other heinous crimes Russians have committed:

1. Execute the crime

2. Laugh and brag

3. Realize the catastrophe

4. Change the story and blame others

https://twitter.com/Tendar/status/1666033978841636866
visionOS supports existing apps for iOS and iPadOS, so UIKit is supported.
More like a few million years. Humans come pre-trained via DNA, the 10-15 years are mainly fine-tuning.
The problem with ChatGPT is it lacks the context depth for more complex tasks - but that is a computation resource limit, not a technical one.
There was a period around 2010 where developers all declared sql dead, and started playing with nosql solutions. My personal experience at the time was, most people didn't have Facebook's scaling problems, and they created terrible tech debts as a result.

Eventually most people remembered why SQL was so great, and they added Redis if they needed a cache. The Ruby people though still liked those NoSQL stuff, and I'll never understand them.
Eh, I might be a whiner, but I seeing that nature.com, I expected something better than a Malcol Gladwell level article.

Okay, the tip with anthropomorphisation is okay, and reminding people that you can't believe in LLMs output is always good... but, like, I'd assume an average Nature reader is smart enough to not need tips like "iterate" or "embrace change".
>At some point the signals going to your brain won't be too different

Tell me you've never had sex. Sex and VR porn no matter how realistic are words apart.
Russia is talking, which means Russia is lying, diverting attention, framing or victim blaming.
Yes. Here is more info from Wikipedia:

Digg's v4 release on August 25, 2010, was marred by site-wide bugs and glitches. Digg users reacted with hostile verbal opposition. Beyond the release, Digg faced problems due to so-called "power users" who would manipulate the article recommendation features to only support one another's postings, flooding the site with articles only from these users and making it impossible to have genuine content from non-power users appear on the front page.[citation needed] Frustrations with the system led to dwindling web traffic, exacerbated by heavy competition from Facebook, whose like buttons started to appear on websites next to Digg's.[19] High staff turnover included the departure of head of business development Matt Van Horn, shortly after v4's release.[20]
I believe the vision pro does do divested rendering. They mention it as a core component of the VisionOS render pipeline.
Agreed, but this was not a solid company in the first place. Rather, Digg was (according to TFA) a failing startup losing money hand over fist that was launching v4 as a hail mary. They were so hard up that no hardware was available for hosting the new environment, so they started reusing v3 servers for v4 while the migration was ongoing.

They bet it all on this v4 thing, and lost.
Right, but that has nothing to do with the Virtualization framework.
"Apple products" and "gaming" usually don't go in the same sentence.

See: the last 30 years of the company.
Plaid isn't a solution to a technical problem. It's a way to deal with the fact that banks don't want their customers to bypass their websites/apps and the cross-selling ads within.
The main issue I have with this paper is that it forgets social network analysis exists. It kind of puts that aside and says whatever propels you to the front, it is merit. But social network status is often governed by many things other then merit. So while merit should be a primary characteristic to evaluate scientists, it cannot be the only one.

What's frustrating is that they argue this from a "who are we hiring" perspective instead of an ideas perspective. If they had made the argument that only ideas with merit can be accepted in science and merit is defined as whatever, then they would be getting somewhere. But they fall into the classic trap of not realizing they are participating in infighting that let's the dominant class succeed in the ongoing class warfare.
Memory is the cheap part at the end of the day.
It's about the rest of the chip and why GPUs are fundamentally and radically different from a CPU.
Yeah, but that's more annoying ;)
That might be true for the admins but for people further up the chain things are going exactly to plan. Third party apps absolutely aren't going to be part of Reddit's future, as evidenced by their ridiculous pricing model. My only criticism is that they didn't announce the sunsetting of the API, although the two are functionally equivalent.
> React Server components require new generation routers, new generation bundlers. They are officially in alpha, and not ready for production. So why is Next.js so pushy about it? I can't avoid feeling that the new direction taken by Next.js is not designed to help developers, but to help Vercel sell React. You can't really sell a service around SPAs: once compiled, a SPA is a single JS file that can be hosted for free anywhere. But a server-side rendered app needs a server to run. And a server is a product that can be sold. Perhaps I'm a conspiracy theorist, but I don't see another reason to break the React ecosystem like this.

I mean, yeah, I see your point.

React should always be self-hostable, full-stop.
Good newsnation coverage as well with Mick West - https://www.youtube.com/watch?v=nDqfGkifPEA

Mick West suggests it's possible that people involved in recovering crashing satellites and reverse engineering may have let their imaginations run wild.

AARO (pentagon) is pushing back on this, but some folks suggest that AARO doesn't have clearance. eg: https://twitter.com/LtTimMcMillan/status/1664383272875376641
Are you using private relay?
I was like "hold on, 2010 wasn't that long ago!" but thinking about it now, things like Github and its code review flow via merge requests only came into my radar at about 2012, and even then it took a long time before it was widely adopted.

Around that time I was in the middle of the Java ecosystem though, which had tons of tooling for validation, linting, verification, books full of best practices, etc.

Still a far cry from what is normal these days, but we did do things like unit tests, end-to-end tests and code reviews back then. But, that was enterprise, the SF web companies I think weren't as enterprisey as the bank I worked for at the time.

It's ironic though; the old fashioned companies I've worked for adopted a lot of the more fast-and-loose-feeling practices from SF, think extreme programming, agile, taking a chance on rewriting the whole back-end to a new language, things like that.
Wait, there are more than one billionaire tech guy taking over a massive social media company?