skysight-inc/HackerNews huggingface dataset:
There’s three kinds of AI safety:

1. “AI is going to (help someone) take over the world”. We don’t need this yet but it’s better to think about it before you need it rather than afterwards.

2. AI is going to do genuinely bad things: generate CP, teach people to make dangerous chemicals.

3. AI is going to do things that people in California think are dangerous: generate a picture of a boob, generate picture of a group of people who are not a mixture of different ethnicities, or sexes, give an answer to a question that isn’t aligned with how people in California think.

China is not concerned with any of these, although it is concerned with its own version of point 3:

3b. Generate criticism of the CCP or anything that the CCP doesn’t like people to know about.
The idea behind frameworks like Flutter and React Native is that you can specify the document as a tree of high-level components, which can then be rendered either as a web page or as a mobile app. In that case, there's simply no equivalent to the semantic HTML tags on the other platforms, so you'd end up with a big impedance mismatch if you tried to force them in there. (Though of course, such tools are definitely targets of OP's derision.)
In my case I would file 2 claims: 1) trademark infringement, and 2) trademark dilution. However, I’ll take a look at these cases and see what claims they filed and maybe supplement if anything applies.

Trademark infringement typically requires “likelihood of confusion”, except where the trademark is famous then there can be trademark dilution even when there is no “likelihood of confusion.”

My trademark is famous, and it’s evidenced by the fact that YouTube and X (and all the other platforms) reserved and protected my trademarked name from being registered and used.

The legal argument would be these platforms are infringing by reserving the name and diluting the famous trademark by not allowing the trademarked account to exist on their platforms.

YouTube and X don’t want to be in Court explaining why they reserve trademarked names and don’t release them to the trademark owner, so it’s just a matter of getting a human involved to get it resolved.
Zepto, a YC-backed 10-min delivery app in India, raises $665M at $3.6B valuation
There's more important things in the universe than those which have economic relevance.

In fact studying things which have no apparent economic relevance is one of the best uses of government dime and has been so, to the great benefit of humanity as a whole, for centuries if not millennia
In 2001 the EU switched (mostly) from a local currency to the euro. For years people would calculate prices back to the currency of old. If you do it nowadays, over 2 decades later, people look at you funny.

People who still rant about the simplicity of jQuery are of the same cloth.
- 90% of Americans have health insurance - I would say it works for more than half (most) of Americans. Granted, not all health insurance is created equally.

- The obesity and congestive heart failure issues is a function of poor dietary choices most Americans make (choosing fast/process food over cooking/making healthy foods), and not a function of healthcare access
Please recommend a quality clone of framework by a chinese manufacturer
The author makes a few good points but on average sounds like an old man complaining about everything. There is a reason React took off, and there is a reason people choose React.

Sure, if you are building a simple content heavy front-end, it doesn't make sense to chose a React framework or React at all. But many apps today come with heavy front-end interactions and have to sync with their back-end in real time. Good luck doing that with jQuery Ajax.

And you can't blame the bootcampers. They were promised riches after a 6 months bootcamp. They were taught React and had little interactions with HTML. So they are doing what anyone else in their position will have done. So when they were out in the market, then React is was. Suddenly, everything became a React component; and if you made a website today, you'd better off start with React.

In defense of React/NextJs: I have been blogging for 10+ years. I started by using WordPress. I have constantly failed to maintain a server up and running for more than a year. There is always something that comes up. A bad WordPress update, DB goes wrong, a failed payment, a bad WordPress plugin update, Server goes down because?, etc...

5 years ago, I switched to NextJS. It's a spaghetti of NPM modules just to build a very static website for very simple content. Sure. But 5 years later, the very same site is still up. There is no maintenance involved as the site is hosted in Github. Not sure I'd say the same about WordPress.
US Bans Kaspersky Software
What if a feature (auth page/module) has aspects that could be reused by other major features too, how/where would you place them?
I’m with OP but we’re a rare breed.
It really is incredible. I’m sure the JS heavy setups have a reason to exist but it’s almost as if people are forgetting that alternatives exist.
I wonder if there's a strong positive correlation between periods of high Federal Fund Rates and periods of prevailing sentiment that espouses for 10x developers.
Thanks for the feedback!

I understand your will to disable vibrations.
But thing is, right now I can’t think of how to offer that option properly. For instance, adding a Setting menu+icon just for that would be lame.

I’ll think about it more, tho.
Please tell me this is a joke / satire
Maybe better url, the official press release : https://www.gilead.com/news-and-press/press-room/press-relea...

@dang
For many people that live where there is no chlorine in the water, it's immediately obvious when there is added chlorine to the tap water. I'm not sure I can taste it, can't remember I've actually tried, but I can absolutely smell it.
That seems like kind of an overreaction. Sure, the first time I saw React I also thought it was an abomination.

But in the end it’s fine. Different, sure, but there really is something to using the same language on both front and back-end, and not having to wonder about how to reconcilliate data and markup.

React and the whole ecosystem gives you a thousand extra problems to care about, but it also takes a ton of them go away. It makes the simple things annoying but the hard things also merely annoying.
is it C64-specific though?
I've got it working on a T4 via Google Colab. The PDF takes 178 milliseconds to the 206 listed in the readme for the C version, so 15%?

https://github.com/fragmede/wc-gpu/blob/main/wc_gpu.ipynb
A PC in 1987 was more likely to have max 640kb of RAM, the "AT compatibles" (286 or better) were expensive still. We had an XT clone (by the company that later rebranded at Acer) bought in 1987 with 512kb RAM.
No, shorting is different; it's borrowing something you might not be able to pay back.

WeWork was signing leases - borrowing real estate. They went bankrupt from not being able to pay for it. This isn't the same as selling shares to VC's. Equity isn't debt.
I literally left front end development because of stuff like this. It felt like insanity. Throwing out the door debuggers, linters, all the tooling so we could express objects as attributes?… and enforce managing state better?..

It felt like a flood of junior programmers in an echo chamber set off by an opportunistic engineers at Facebook who were more interested in creating their own job security then work to evolve an existing standard.

Seriously who honestly thinks that the authors and governing board of HTML and CSS didn’t closely consider the features in react?

What kind of arrogance does it take to say they’re fucking dumb let’s reinvent EVERY tool on front end because we know better.

But I digress…
We had a cluster of about 8 X-terminals which were connected to a HP-UX box of some sort at my university. My "running Linux since 10th grade" ass had a fast-pass when everyone else had to queue on one side of the hall for a Windows machine or the other for an OS 9 Macintosh
Everything you just wrote is either wrong or even exactly the opposite.
The author of the article might be blunt and you might not like that in your mind things seem different, but the problems he highlights are real.
For better or worse, part of the story of the FOSS ecosystem is that there is no singular "Linux community." Rather, there are many communities with different interests, some of them overlapping, some of them complementary, and some of them competing. There are plenty of detractors to modern technologies such as systemd and Wayland, but there are also plenty of supporters (or else those technologies wouldn't have gotten adopted in the first place), and there are people who don't have a passionate opinion one way or the other as long as their software works.

This lack of a singular community is simultaneously a blessing and a curse. It's a blessing due to the freedom FOSS software provides; not all software is going to fit everybody's needs, and FOSS allows the freedom to modify software tools. However, the curses are resources spread thinly across competing projects, as well as the rough, sometimes chaotic development cycles that sometimes occur in bazaar-style projects that lack Steve Jobs-esque "benevolent dictators" who have a clear vision for the product being developed. For example, the transition from X to Wayland would've probably gone smoother if there were a powerful entity that was able to enforce its will among Linux users and developers, but since there is no singular Linux community, the "bazaar" independently adopted Wayland at each project's own pace. This is the fundamental difference between Linux versus platforms whose vendors exert greater control, such as Windows and especially macOS.
> all of that doesn't change the fact that the code above is hyperscript, not htmx

--- start quote ---

https://htmx.org/

htmx gives you access to AJAX, CSS Transitions, WebSockets and Server Sent Events directly in HTML, using attributes: https://htmx.org/reference/#attributes

--- end quote ---

All my examples come directly from htmx documentation
What do you think of the wave of companies trying to cash in on inexpensive labor from countries in Africa?

My experience working as a vendor to a company that hired Zimworks out of Zimbabwe was rather underwhelming. Pastoral care was all they offered for healthcare to the local Zimbabwean employees, and the time shift the local employees endured seemed to wear heavily on them.
I was recently on a project where the backend was written in Python and finished in two months. The frontend guys are still dicking around with React components eight months after the project started. The front end on this project is child's
compared to the backend. It's frustrating.

There was a point in the history of front-end dev when they all started calling themselves "rock stars" and became convinced that they are the future of software development. The SPA trend gave frontend devs an excuse to write unmaintainable code, gave designers an excuse to call themselves software developers, and then they all told the world they are doing "full-stack development" when Node appeared. Meanwhile they never bothered to learn pre-SPA UI, UX, or content design principles.

Thing is, working on front end never gives you a chance to work on problems that backend has to deal with. I never let JS guys work on backend code, because they are lost if they cannot find a module online that does what they are asked to do, or is missing half of the features from the spec it promised to implement (always the hard ones). We then have to pick up the mess and rewrite it in Python or Golang, which is wast of time and money. I once quit when when the client showed me the Python code written by a JS dev. My devs refused to touch that shit and we went to work for another client.
Now let's investigate JetBrains. Untill recently they had huge presence in St Petersburg and relocated their Russian staff after war broke out.

IMO it is supply chain risk which ought to be carefully audited.
Great doco about origami that Erik appears in. 'Between The Folds' https://www.youtube.com/watch?v=DiIr7du6Y3w
> Screen readers and other assistive technology fully expects your HTML to be semantic.

No they don't. They were developed to work on the web as it existed at the time and handle it fine. A screenreader doesn't magically do something different and better with an <em> tag than a <b> tag, and only confused thinking and propaganda has made people think so. (And anyone who actually cared enough to test with a screenreader would know this - but people don't actually care about screenreaders, they just use them as a stick to beat technologies they don't like)

> CSS tends to be hard because (1) people insists on having a single page with a single stylesheet and (2) only divs are used, and so they use class names for everything.

> If you didn’t use a SPA you’d have scoping. If you used semantic HTML you could target based on semantic structure. Both of these makes CSS easier.

You still need class names, because you're always going to have some distinctions that matter in your domain but can't be mapped onto the fixed list of HTML tags. So either you use divs and class names for everything, or you use a mix of tags and use a mix of class names and tag names, which just ends up being less consistent and more confusing.

You have components that are shared between pages, so you either have to include all your CSS on every page, you manually figure out which components are used on which pages and make mistakes sometimes (leaving you with missing styles), or you use a Javascript UI framework.

> JavaScript is fine to use if you have to. But using JavaScript when you don’t is just wasting time.

I find the opposite. You're always going to need JavaScript eventually. Trying to do stuff with CSS and HTML tags just wastes your time and the end result ends up being more complicated because it's a mishmash of both. If you use a well-known JavaScript UI framework from day 1, it's so much easier to end up with a simple, consistent, maintainable site.
How to stop Perplexity and save the web from bad AI
Canonical tried and failed many times to be the driver behind improvements to Linux and the Linux desktop. They want control and influence across the stack, but so far their biggest bets have mostly been failures.

They pushed Upstart. It fell to systemd.

They pushed Unity. It fell to GNOME.

They pushed Mir. It fell to Wayland.

They pushed bazaar. It fell to git.

And so on.

Also worth noting that they've never been big contributors to the Linux kernel itself. Top contributors include Intel, AMD, Red Hat, Google, Meta, Linaro, SUSE. Even Oracle.

Canonical? Nowhere to be seen.
I built a fairly successful vc funded startup with a front end lead that thought this way about frontend frameworks. For a suitably complex application what happens is that you end up organically building your own framework in order to manage the mess of application state that is the screen. Now in order to spin up, new engineers need to learn this unusual organic framework to get things done rather than just use the excellently documented React that they likely already know.
From the paper's analysis of the wine - it should be safe to drink, but most likely disgusting. The amount of lead or other bad things isn't particularly high if you just have a bottle.

Now, what would be the oldest enjoyable wine? The oldest that we have any record of anyone enjoying was the 1540 Steinwein, drank at age 421 in 1961 by Hugh Johnson, who took notes: "...We were able to take about two sips of the centuries-old substance, before it died of exposure to the air, gave up its spirit." [0] This is actually common in wines that are past their peak - a brief moment of life before they die forever from the air. One bottle remains but with the notes by Johnson I imagine that the wine will die before it is next tasted; it is "on loan from the Simon family from London."

With time, I expect the record for oldest enjoyable wine to be taken by either madeira (possibly from 1715) or the Rüdesheimer wine from 1653; in 2013, Edwin Vos from Christie's sampled a 1715 JCA & C Terrantez bottle and called it "remarkably youthful and surprisingly sweet." The last person to try the 1653 Rüdesheimer wine was Queen Elisabeth, I can't find her tasting notes :)

For the casual drinker, who wants to drink old wines at home, good options are madeira, port and sauternes. Even if the bottles are past their drinking window, they will still be enjoyable.

[0] https://www.buergerspital.de/wineestate/1540-steinwein/index...
Docker is difficult, k8s is impossible.
Thank you. I'm at a css in js company and everything you wrote about it is The Truth. We've got nav menus written in reams of javascript. Stuff that could be done with zero js, or a couple of lines of glue. In a previous role I used Ant Design which were on the SASS train, trying to override the specificity of their stupidly long selectors was painful.

React is too loose, it just enforces no abstraction or discipline. JSX ends up an ugly nightmare of angle brackets, ampersands and question marks. You often have to piece together how the component works by staring at all the event handler code for minutes hours days. Most of my colleagues writing it would stare blankly if I mentioned MVC. I think I would come down on the side of Angular, it's opinionated, but at least they attempted to separate the template from the controller, and logic in the services.
Well said. Also been doing this since the 90s. I still like discovering new sites, blogs and creative things people make. HN is one of the better sites for that.
FWIW, Google explicitly says it mostly ignores semantic HTML [0]:

> Having your headings in semantic order is fantastic for screen readers, but from Google Search perspective, it doesn't matter if you're using them out of order. The web in general is not valid HTML, so Google Search can rarely depend on semantic meanings hidden in the HTML specification.

And a typical business web page likely won't have many "automated processes" it wants to accommodate except for search engine crawlers.

[0] https://developers.google.com/search/docs/fundamentals/seo-s...
It’s like asking why you would use a list anyway and not just a bunch of BR or P tags
I see. Interesting. But what’s the benefit of using a tool like that if you’re only targeting the web as a platform?
Ask HN: How many AGI researchers have/are studying philosophy seriously?
Just asking. Philosophy by itself just seems to be THE important thing to study and maybe research on the road to creating an understanding artificial mind. And "deep learning", "free energy principle"... were these produced with help of theories with philosophical insight, systematically?

Seriously. 'Existential' (epistemological+influential) power of AGI by definition (sorry, no definition, read it like "in my opinion") encompasses "all of science" or at least some "analog" of science (working somewhat differently than "human science"), in which there will be analogs of all human sciences nonetheless. I want to put forth my opinion that it's foolish to search for some numb mathematical formalism, one that isn't informed by philosophical theories, in hopes that it will generate all of science or comparable. That's too primitive. Remember that scientists from different fields have different cognitive styles, different sciences have different philosophy, methodology, paradigms, the "style of mental content". AGI by definition (or in my opinion) will present a unified understanding of all of them from a "sufficiently philosophically powerful/abstract" philosophical foundation. So why not work on that theory?
https://news.ycombinator.com/item?id=40746543

Nothing in the htmx docs shows it's optional.
Do the new magsafe pins burn out after a year or two like the old ones? Or the cable insulation sloughs off?
And then of course you had to buy an entire new proprietary charger from Apple, not just a 3rd party cable. Or even take the laptop to Apple to replace the laptop's magsafe connector.
I did give some thought whether your native language makes it easier or harder to learn others, but all I have is anecdotal cases from my life. I wonder if there are any scientific studies on the topic.

E.g. a curious thing I noticed is the frequent complaint about Latin being very hard to learn because of the seven grammatical cases, three genders and morphology -- words just don't stay the same. As native Russian speaker I find these things absolutely normal and easy to understand, but I can image this must be a nightmare after English.

Slavic languages you mention are very curious in how different yet how similar they all are. One of the most impressive thing I saw with respect to learning languages is the Interslavic language [1]. Apparently if you speak any of Slavic languages you can understand it quite well, even though you usually are completely lost with most of the other Slavic languages. You still need to learn to speak it, but the fact that you understand foreigners with zero training just blows my mind. Feels like you awakened the memory of your ancestors of something.

[1] https://www.youtube.com/watch?v=NztgXMLwv4A&t=122s
Sometimes I choose React because it’s easier for me, despite it adding unnecessary complexity to the project.

For example, I’m terrible at front end, and design. Tailwind has a React library that handles many of the UI requirements and produces a decent-looking front end with minimal effort. I know enough React that the complexity doesn’t scare me, and there’s so much documentation and training available that it’s easy to find answers. It integrates easily with other frameworks. I can reuse components I built for other projects.

React is often not the optimal choice for the project, but can yet still be the right choice.
I don’t think it’s fair to blame React for the flood of shitty people. It’s a symptom of the problem, not the cause.

If I had to manage the collapsing house in Rust I imagine it’d be much, much worse (though I can’t say I ever had that experience, so who knows?).
Given this is a photo of Sudan, i think the more striking thing to imagine would be the current famine in Sudan, given it is the same country as the photo was taken in, and we are basically repeating history right now.

[I'm not saying there aren't other people who suffer in the world, just in terms of history repeating itself, i think the Sudan case is much more direct]
Reproducible Builds are quite common now, there is even a movement about them:

https://reproducible-builds.org/
It seems he certainly hit a nerve here, regardless of people's position on the subject...
We need more CPU manufacturers not just a Qualcomm monopoly.
Right. I hear you.

Pretend I'm a person who agrees with you about React (I might be, after all[1]).

Have you ever seen that page "You might not need Jquery"? Can you please write a similar blog post (or even put it into a comment here so that I can bookmark it) titled "You Might Not Need React"?

I want to know what it is that React gives (maybe)millions of developers that you don't need.

All those things that React is commonly used for: what are you using instead? Show snippets, please.

So, yeah, throw me a bone here, please write "You Might Not Need React", because I can guarantee you that there are numerous devs who want to read such a post.

Pretty please.

[1] I looked at the React tech stack and learning curve for someone who only knows HTML, CSS and Javascript out of the entire web-stack, and noped right out of it.
If you don't wish to be reliant on academics being able to study disinformation for you, the second best thing might be to read the textbooks that teach how it is produced.

(originally: https://news.ycombinator.com/item?id=40683645 )