skysight-inc/HackerNews huggingface dataset:
Hello, creator and maintainer of Nodezator here.

> seems like there’s also a general feeling that this is easier than learning how to code, and I guess my question is… is it?

IMHO, node-based programming will never and should never replace text-based programming. Neither is in fact a replacement for the other. There are problems that benefit more from one approach and other problems that benefit more from the other one. There are also many problems that benefit from the cooperation between both approaches. There's even problems for which we should use neither, for instance, when a spreadsheet would suffice.

Unfortunately, many node editor projects sell/promote their tools as silver bullets that will solve all people's problems and replace all their tooling. I think this attitude prevented a more wide adoption of node editors and harmed their reputation a lot. It also prevented a lot of experimentation with them that could have led to more established and efficient workflows.

In the Nodezator project, it is quite the contrary. I only recommend the usage of a node editor, including my own, for specific problems for which node editors are better suited.

Which kind of problems are that? Well, since node editors are still not used much as tools for general computing, we only know about specific domains, like media compositing, for instance. There's much to be researched and experimented still.

I myself use Nodezator for generating position animation data for a 2D game as well as images that I use in video editing workflows in other apps. This year I've been very busy with development work so I didn't do much research, but since last year I've been experimenting with a lot of different tasks and documented my findings a bit. I'm only scratching the surface though. Experimented with SVG image generation and even parametric generation of 3D models. If you want to know more, you can check this thread on twitter/x: https://x.com/KennedyRichard/status/1747605744361300126

I'd also like to experiment more with workflows for non-programmers in the future (for instance, where someone designs a set of nodes and only teaches a non-programmer how to combine them for various tasks), although I already expect node editors to succeed in various domains regarding this (but as I said before, never replace text-based programming). The reason is that it already is used like that with success in other software. For instance, in Blender 3D, where non-programmers use their node editor for many different 3D-related workflows.
Marcus Aurelius' Meditations:

"The mind adapts and converts to its own purposes the obstacle to our acting. The impediment to action advances action. What stands in the way becomes the way."
I'll invoke Cunningham's Law here. If I remember correctly, Wayland was designed to support a wider range of display targets than X11, such as set-top displays, car dashboards, and other specialized systems. In these cases, the full functionality of a traditional desktop environment isn't required, so it isn't included in the base system.
Ha it’s already a severely impacted field. Every other computer programmer that doesn’t live in a city is a woodworker.
I had to realize that at least in start up world most (non db focused) devs thing they might not be experts in SQL but have a very solid understanding

... and then don't know about a lot of very fundamental important parts and are blissfully unaware about that, too.

And to be clear I'm not saying they don't remember the exact details of something.

What I mean they don't even know that there are things they have to look up, nor any experience or willingness to understand what they did wrong by consulting the official documentation instead of just randomly googling and trying out "solutions" until one seem to happen to work.

The most common example would be having so little understanding about transaction that they believe transactions are just magically fixing all race conditions, and then then being very surprised that they don't. Or believing that transactions in SQL are fundamentally broken after realizing that somehow their databases got corrupted.

And again I don't mean junior deves, but people with 10+ years of backend or "fullstack" experience, i.e. people which at least should know that when to consult documentation/lookup protections transactions provide etc.

I have seen more then one time a (final state of) the situation where people started with believing SQL transaction magically fix everything, then get "corrupted" data then blame SQL for being broken and move to NoSql.

The joke here is all the concurrency problem are very fundamental and independent of SQL vs. NoSQL.

And SQL often gives you more powerful/easy to use (at small scale) tools to enforce synchronization, but at a cost. While NoSQL often gives you harder to use primitives where you have to do much more outside of the database to guarantee correctness, but then at least you will more likely blame you code instead of the db for things not working.

The most ironic thing here is I'm not a db expert, I just know where my knowledge stops and where I can lookup the missing parts and can't even give you much tips about huge dbs in production luckily surprisingly many companies have comparatively "small" db needs.

And honest where I see race condition related issues in SQL quite often I'm rarely not seeing them in NoSQL code. Where this issues in SQL make me sad as they are often very avoidable in NoSQL I often feel like giving up in resignation.

Through that experience is for "smallish" databases not Twillo scale. But a surprising large amount of companies have surprisingly "smallish" databases. Like no joke I have seen companies being very vocal about their "huge database" and then you realize it's like 5GiB ;=)

Honestly I (metaphorically speaking) don't even want to know how db experts feel about this, I'm not a db expert and just have a solid enough foundation to know where my knowledge stops and when I have to look things up (which is all the time, because I'm not writing that much SQL).
Bad propaganda, but whatever I'll bite.

If you have a nation of gasoline cars, you can only use gasoline to move them.

If you have a nation of EVs, you can use coal ... or solar ... or wind ... or geothermal ... or natural gas ... or nuclear to move them.

ICEs are really, what, 20-30% efficient? While coal in a powerplant is likely 37% efficient. Transmission losses is 5%, then the EV is 90% efficient in power to wheels.

And again, if your entire nation's transportation is EVs, you can change the source of electricity by replacing the plants. If your nation's transportation is gasoline ... you can only use gasoline. There is no path to transition.

Sodium Ion batteries in the 150 wh/kg should enable a dirt dirt cheap 200 mile range city car, and should be able to do almost 300 mile range cars as well. 200+ wh/kg LFP should be able to do 300-400 mile cars.
IME there is a general consensus:

Routing: react router (not very good imo but widely accepted and good enough)

state: No libraries. Just use “useState” and if necessary “useReducer”

Builds: vite

Then pick a query caching library so you don’t need to treat fetched data like its application state… ReactQuery is widely accepted and very good. Apollo if you’re using graphql
The conspiracy theory factories are going to have a field day with this one!
It's so weird how some irrational germaphobes fetishized masks over a minor respiratory disease with a >99% survival rate. Masks are marginally effective in preventing transmission, if at all. And since SARS-CoV-2 was always destinated to become endemic the masks were totally pointless anyway. All of us are going to occasionally get infected no matter what we do.
Hard to avoid some tribal knowledge. To be free of it you need full reference documentation and tutorials for everything you do. And to update it as you go. And to realize what might be missing from a paedagogical perspective. Not easy and probably not possible for a commercial operation. And not necessary. 80-20 rule applies.
I see the progressive nature of the US tax system as described in the article as a wonderful achievement of the 20th century. Sure, I think the more progressive tax of the 1940s through 1960s was a hell of a lot better for building a middle class, but we're still doing ok.
Absolutely they would. It's soooo easy to lose sleep, and unfortunately getting it back isn't really a thing, not unless you want to use up more time. I guess we need to keep reducing the need for sleep until it's short enough it can be conveniently done anywhere, anytime!
> And should I stress again that there is absolutely zero positive tradeoffs?

Just because you don't value or acknowledge them doesn't mean they don't exist.
And that's okay. Most applications don't need zero-downtime deployments, and there are already plenty of APIs that support that use case. I'd rather have more like this one.
Have you ever listened to what Lemoine said? Sure, we have no proof and he's under NDA so probably no documentation that can be scrutinized. But still, his alleged chats were chilling in some ways. They probably didn't except him to go public and so they had to spend years nerfing their chat bot before launching it as a product and that's why it sucks: They're too careful and have too much to lose in bonuses. Google will probably lose some market share over the next few years before they're getting nervous to put someone with a longer leash into the CEO seat.
Margarine? Fruit loops? Canola oil? Snickers?

I dare you to make actual snickers with the same ingredients outside a factory. Refining the sugar alone is a huge industrial process.

Even the US's entire grain supply is sprayed with folic acid. So pretty much all wheat and rice that you find at the grocery store is also disqualified.
Atlassian Rovo is this.

The trick is to get people to get their tribal knowledge down in public Slack channels or their docs system.

Recording most Zooms with AI summaries may help.
Sei AI (YC W22) Is Hiring an AI/ML Engineer with LLM Exposure
You may very well get more out of, and put more into the couter-offered position. It would suck to work 5 months knowing you're leaving a company that values you this much, and willing to pay extra to keep you on board and happy again.

To my mind, moving onto the new contract would be a mistake. You don't even know if that'll work out. You know that the counter offer will.
Did no one watch the talk? :) After 13 minutes it ends and tells you to go to a IAI website to continue to watch. Fucking infuriating.
Hasn't JS caught up with jQuery mostly?

* x-platform (that was a big thing in jQuery in the beginning): solved in JS

* DOM selection (not as elegant w/o some aliassing, but still): solved in JS

* making XHR: solved in JS

* building plugins: solved in JS

* method().chaining().style().of().programming(): not in JS

That's mostly I think.
There are lots of reasons to do slow rollouts. You should be rolling out in stages anyway.
> A one-to-one mapping is not structure preserving.

That's just the point we were making: if you mess with the structure of natural language, then language models don't learn it as well any more.

The transformations do preserve the entropy in the sense that the lowest achievable perplexity is the same for everything except the nondeterministic shuffle. Since applying a one-to-one function preserves the entropy of a discrete random variable, in this case the random variable over documents in the training and test sets. In principle, a universal approximator should be able to learn to invert any one-to-one transformation we apply, although of course in practice a GPT architecture doesn't achieve this.

The transformations do mess up the local entropy in strings. But I think that's part of the point. Human language seems to be structured in a way so that things are locally predictable. When you screw up that structure, then languages are harder to learn.

We are working on a followup with more transformations including syntactic ones, as you might imagine. It's surprisingly hard to come up with manipulations that target specific aspect of linguistic structure, while fitting the criteria that (1) they don't affect the lowest achievable perplexity, (2) they clearly change the language from "possible" to "impossible" in a way that all or most linguists would agree with, (3) they can actually be implemented using the data we have---for example a transformation that relies on detailed syntactic parses would require that we parse the whole dataset, which is not only time consuming but also introduces possible confounds from errors in the parser, etc. We're talking to a lot of people, if you have ideas we'd be happy to hear them!
> Who was claiming 3.4%?

https://www.instagram.com/thejrecompanion/reel/DCxS6R9SiZM/

https://www.factcheck.org/2020/03/trump-and-the-coronavirus-...
> But I think indentation is better for visualising block structure.

Which is irrelevant, because you can visualize code however you want via editor extensions.

> And yeah, I am definitely coming for Lisp.

An endeavor which is simultaneously hopeless and pointless.
I imagine this is more of a functional issue. i.e., the loop buffer caused corruption of the instruction stream under some weird specific circumstances. Spectre and Meltdown are not functional issues but rather just side channel issues.

This should be fun, however, for someone with enough time to chase down and try and find the bug. Depending on the consequences of the bug and the conditions under which it hits, maybe you could even write an exploit (either going from JavaScript to the browser or from user mode to the kernel) with it :) Though, I strongly suspect that reverse engineering and weaponizing the bug without any insider knowledge will be exceedingly difficult. And, anyways, there's also a decent chance this issue just leads to a hang/livelock/MCE which would make it pointless to exploit.
Hello, everyone! Creator and maintainer of Nodezator here!

Oh, so this post is the reason why the traffic for Nodezator's GitHub repo has been spiking today. I already replied to a few questions here, but I won't be able to do many more today. I'll try to answer all of them over the time though, so ask as much as you'd like. Thank you for taking a look at my tool and for all the feedback provided, it is much, genuinely appreciated.
>Then there are engineers (and people in every profession) who never try for the entirety of their careers, and this is the majority of every profession.

I find this pretty ridiculous. It's just that the standards are pretty low in IT. And being a good programmer just isn't a job requirement in the industry. I don't know a single case where a someone got fired for writing bad code.
We can start by asking, "What are the epistemologies that exist within psychology?"
Agreed. The false analogy just reduces the likelihood that a real dialogue starts because it’s faux boogie men.
are you sure? W comes before X....................................................................................................................
Not RLHF, but my understanding was they heavily use that data and it was a big part of their moat, part of why competitors wanted to clone their results because they couldn't derive as good of quality from the web alone (Microsoft used the bing toolbar to clone them in the 2010s).
Not clear (to me) in the original post -- was this done accidentally or intentionally?
> You still need to access the DOM, which can't be done directly from WASM. Maybe someday it will happen?

You can access the DOM through JavaScript glue. These Rust WASM frameworks do that:

- Leptos: https://www.leptos.dev/

- Sycamore: https://sycamore.dev/

- Yew: https://yew.rs/

- Dioxus: https://dioxuslabs.com/

Eventually you won't need the glue.

> Okay, so use canvas instead and do all UI inside WASM?

You can do that too. That's what this VB6 clone written in C# and compiled to WebAssembly does:

- https://bandysc.github.io/AvaloniaVisualBasic6/

- https://github.com/BAndysc/AvaloniaVisualBasic6

> vague "JavaScript limitations"

It's not vague. Despite 28 years of effort optimizing JavaScript, WebAssembly outperforms it:

- https://nuenki.app/blog/bloom_filters_optimisation

- https://jordaneldredge.com/blog/speeding-up-winamps-music-vi...

- https://www.amazon.science/blog/how-prime-video-updates-its-...

- https://web.dev/case-studies/google-sheets-wasmgc

That's a kick to the groin that's tough to walk off.
Good point, but you should take a look at a post where he does exactly this: https://infrequently.org/2024/08/object-lesson/
You mean the Google sidebar in the Pixel launcher with Google News that replaced Google Now? Yeah, that was awful. But you could disable it in either the launcher settings or the Google app itself. I'm glad I'm on GrapheneOS now.
Problem is that for strawberries or diamonds or SV startup stuff there is a line where if you make something infinitely available it will also loose the value.

You cannot equate paper clip maximizer with SV companies. Because fitness functions are different.

Not saying that diamonds industry didn’t make world worse off but still somehow it didn’t take over the world to make people eat diamonds for breakfast. So the same there will be no entity that can make all people everywhere eat strawberries for breakfast all year long.

Scary part is finance industry that basically already is self conscious with all the rules baked in and no single person being able to grasp it.

Finance with AGI could already become paper clip optimizer - but it actually needs energy only. It doesn’t need humans anymore. So it would most likely fill in whole world with power plants and erase all other life just to have the electricity.
sounds like there's a market for a woodshop in the city, gym membership style.
Every time I use Facebook (which isn't many but still) I am re-shocked at how fucking SLOW it is. How many times I end up refreshing the page because some damn thing didn't connect quick enough, or maybe too quick and it wasn't ready, I'm not sure.

YouTube is also great for this, like, 1/50 navigation clicks just results in a blank page with no error message. Ctrl-R to the rescue.

Or the number of times Reddit's infinite scroll just... dies. Somewhere in the background, I don't know where.

Like I can't think of any of these major platform websites where shit isn't just constantly tripping over it's own dick and breaking in often humorous but also just ridiculous ways.
Experienced internet users, what use cases do you have for an internet search? For me it is one of:

a. I know what website has this information and I go directly there (e.g. Wikipedia or Github or Google Maps)

b. I need a real human opinion or feedback (usually a Google search by Reddit domain only)

c. I need some well-known information that is easy to verify and this is the problem LLMs are very good at

This is >95% of my "surfing" activity. I think I would barely notice major search engines going down one day.
I was thinking of a case like this:

if (foo)
return;

Perfectly valid and people do it. But then later on someone might put a debug statement above the return to check something. Or add some other logic.

if (foo)
doSomething();
return;

And suddenly the logic is broken and the return falls out of the if-condition. It looks fairly contrived with an example like this but easy to do when code is a bit more complicated or people are tired or rushed. It's a good habit to always enforce braces for if-conditions as it defeats that whole category of mistakes. Fairly innocent but can be so hard to find because of that.

A linter would enforce having braces and solve the issue. And for codebases without a linter it is a good habit to just go with the braces.
If you lose your house keys, you don't have to give up your house and all your furniture. You are allowed to pay a locksmith or break a windows, you own it after all.
I wonder if the Franework model will ever apply to cars with modern safety. Probably not but one can dream.

I want an electric car.
I also wish it was feasible to work on it.
I was going to write a counter argument that codebases using earlier versions of React did not look nice, and that they only started to look nice when React moved to Hooks and functional components.

But I realized that actually supports your argument. React with Hooks and functional components unseated old school React.
To be fair, this kind of spying is quite outdated and inefficient.

What is easier is a Chinese company establishes a branch in the US that barely has any operation. But they then try to poach experienced Chinese-born workers in other US companies with high salary, good perks (paid travel to the Chinese HQ for example, who doesn't want to visit home and have the entire trip expensed?), generous PTO, etc.

They easily get the talents and industry knowledge from these hires. One person does not need to know or say everything, but a little piece from dozens of experienced employees coming from multiple industry leaders paint quite a comprehensive picture eventually.

And it is legal, and the participants can easily or unwillingly share critical information without raising any security flags since they are "protected" by the Chinese company. Any legal proceeding or investigations has to go through the corporation first so it is much more difficult for the US to handle these cases.
Mr Appleseed was working his magic to plant a future for delicious apple juice booze. They should’ve called him Cider Claus.
Unlocking the Power of DynamoDB: A Developer's Journey
How much of an assurance do you want? I've been using btrfs on my desktop for 3+ years. And I've also experienced no issues thus far.
Show HN: Sagaweave – AI storytelling app for non-writers
Hi HN,
I’ve just launched Sagaweave, an AI-powered storytelling app to help individuals create their own fiction. It uses Hermes to help craft engaging stories and improve creative writing. Very early stages.

[Link to project](https://sagaweave.com)

Features:
- AI-assisted story generation
- Uncensored storytelling (optional)

I’d love to hear your thoughts. Do any of you use non-AI writing apps (like Wattpad)? What could get you to switch over? Thanks!
I can't tell. My phone is as vanilla as it gets.
Zig has been around for 9 years, and it looks like 1.0 is not even in the cards. Seeing a lot of flux, with lots of unresolved issues (per its GitHub).
4,096 iirc, and i also was one to arbitrarily split files lol
I tried several times to find some specific reel I saw in Instagram and had a really poor experience. Results were not only what I was looking for, but seemingly off-topic completely. Understandably, video content is harder to index if author does not put effort to give more context.
Thinking of how I'd do this for ZFS... I think I'd do something like: add a layer that can read other filesystem types and synthesize ZFS block pointers, then ZFS could read other filesystems, and as it writes it could rewrite the whole thing slowly. If ZFS had block pointer rewrite (and I've explained here before why it does not and cannot have BP rewrite caoabilities, not being a proper CAS filesystem), one could just make it rewrite the whole thing to finish the conversion.
Except for those car machines
You aren't using the internet, you are using Reddit as a walled garden. This is risky if you believe a decentralized internet is valuable
Which topics are you looking for resources on?
>when our brains evolved for stories. But that's for another comment

Go ahead !
The very first time I used rust for a work project, I tried to implement a tree... well actually I tried to implement a linked list first, later hoping to expand it into a graph.

The distinction that's aggravating me is the compiler refuses to compile code that I know is correct, but it's not smart enough to prove it, so it just gives me the finger instead.
> Get full access to this article View all access and purchase options for this article.

Uhm, screw you?