skysight-inc/HackerNews huggingface dataset:
> it was explicitly pushed and advertised as such

I'm sure React fans who misunderstood the virtual DOM (which was explicitly advertised because it was the most popular part of React[1] vs the other parts that people were more critical of) may have said this, but I never saw the project itself advertising itself as faster than vanilla JS, only that it could be faster than competing frameworks, _especially_ ones that rebuilt the DOM unnecessarily.

> I dunno, I used Redux for a few years

Redux is a different library than React. State management across an app is a problem even for non-React applications, it's not like React _uniquely requires_ work to address state management.

I don't see why your dissatisfaction with Redux has anything to do with React making a very specific and buggy part of building web apps easier to manage in return for a performance cost and following its API.

[1]: See mention near the end of https://medium.com/@dan_abramov/youre-missing-the-point-of-r...
Postgrest + Petite-vue + One of the many classless css frameworks.
Surf: A simple web browser based on WebKit2/GTK+
Yeah, the potential for enshittification is massive. I can imagine they'll offer the Wi-Fi for free at first, use that as a reason to take out screens, and then start charging for the Wi-Fi as an "extra service" (in the way that everything is charged for these days, including basics like booking seats together if you're booking for two or more people).
Earthquake Fish
All of the PWAs on my iPhone running 17.4 will now open in Safari instead of in fullscreen, and iOS itself warned me the first time I opened a PWA from the home screen after installing 17.4 that iOS will now open all „linked websites“ in the „configured default browser“.

They’re obviously trying to prevent companies from bypassing their extortion proposal in response to DMA by simply offering a PWA to users that can work around the „core tech fee“..
You’d rather write a bunch of nested React.createElement calls due to some unjustified religious hangup?

JSX is sugar for a tree, it’s not that complicated
Backend: FastAPI + Pydantic + SQLModel (Python)
Forntend: Vue/Nuxt
Database: Postgres
Things like the below are precisely why I would not only bet on Google failing but silently hope that they do.

Sorry, Gemini Advanced isn't available for you

Gemini Advanced is not yet available in some countries, for work accounts, or for users under a certain age.

Rant:

No explanation, no suggested alternative; just an ominous "Learn More" button that sends you barreling down the spiraling rabbit hole of support.google.com. Diving deeper, I uncovered that 's accessibility is limited to personal accounts under Google One with the sole Workspace option being for Google Workspace Individual(??).

On my personal account I can sign up for Gemini Advanced by upgrading my Google One account to Google One AI Premium.

As a standard Google Workspace account holder, I was directed towards Gemini for Workspace but naturally that is still branded as Duet AI for Workspace..
And naturally I have to request a trial and be contacted by a Google team member even though it has been announced as being generally available..

It's a microcosm of the broader frustrations with Google's approach to product development and user engagement that we've come to expect - hyped product launches with restricted availability, arbitrary limitations, and a consistently-confused product ecosystem.
very small and indie, but i’ve really enjoyed SpinalCMS.
It has to be public (or at least not too locked down) or things like Address Book in outlook would stop working. Lots of weird things depend on the LDAP tree being broadly accessible. It's just that it leaks more information than most people think.
It does, and I had exactly that same reaction! Regexes are a leaky abstraction, like all of them.
Thanks for commenting!

This is a great point, in fact is the main purpose of the model. The model is validated against genomes with variations which were never seen to check its prediction capabilities.

AFAIK, variants are created either by changing/adding/shuffling already known genes. And not trying to create an unknown mutation of a gene we never saw before. Therefore, our thesis is that with enough information we can capture the effect of the gene in the final product.

Of course, there is epigenetics as well; which is tackled with additional information about the environment.
And that's OP's fault how? We often have to work with the environment and framework we have, not the one we wish we had where we could just immediately implement the best possible solution.
> Require some kind of insurance/escrow/backup in advance

This is kind of ridiculous in this context. The content is not really at risk of being lost. Did the service go away even though you were supposed to have permanent access? Okay, now it should be legal for you to download it from The Pirate Bay.
Unless it touches hardware.
The argument espoused should be examined more directly for things you agree with, otherwise one risks becoming a hypocrite.
many use it badly, indeed. but is React evolving in a way that makes it easier to not use it badly?
React's original problem was that its users were expecting a framework and got a library. It's not semantics what matters here, but the fact it didn't take care of fundamental parts of web apps, leaving those to be handled by someone else. And the result was often a buggy, half-working slow app, due to a mismatch of different modules. In my opinion, it is kind of like the "C" of web languages, in a way. It is powerful, but certain concepts are difficult to master and leave out too many important features.

This is why nextJS is becoming so popular.
The upside though is that you are usually well paid in this field so a lot of us have the choice of doing less paid work and do impactful work without getting paid. (But yeah, I hear you, it does feel like the system is rigged for depressing results as a whole)
I ran a web dev business for 20 years. It includes two sites you probably have visited and bought things from. We used HTML for HTML. CSS for CSS and Javascript for Javascript.

Then we used a common and popular programming language to make them all work together.

It was compatible with everything. Worked everywhere. Interfaced with everything. And was as fast as hell.

No additional thinking or learning required.
For Eco friendly Canada! Let everybody use only public transportation and bicycles in Canada!
The thing is, company can put literally anything they want in their ToS, they can say we're free to break your legs for any reason whatsoever at any point of our choosing, that won't make it legal. Courts frequently rule based on the customer's and market expectation vs what ToS say all the time, and the consumer wins more often than not.
What he is saying is he didn't pay attention to that detail, for one reason or another.
And the fun part is that there are many folks out there, that still argue that there's no need for climate regulation for example, because left to its own devices, the free market will do the "right thing." But clearly because of the tragedy of the commons and things such as the climate often being seen as an externality, you need something external like governmental regulation to make sure that the right thing is done.

Of course it doesn't help that governments tend to also be annoyingly inept at this, but at least they have more of a chance to get something done for this.
from the parent:

> TBH I would just recommend using that and all its under-the-radar features (like grammar, and built in function calling support with Functionary).

I never heard about Functionary, this comment seems to say “I would use llama.cpp plus Functionary”. Now, since llama.cpp allows to plug in several models, I was wondering if Functionary works with several models too, ie is Functionary a library that allows to add function calling to models?

The following answer to my comment helped clarifying that Functionary is not a lib, but a specific model, or that is what I understand from the answer. So the answer is “no, you can’t use functionary with many models (eg it’s not like llama.cpp that works with multiple models) because Functionary is a model itself”

:-)
How to use meditation to defeat procrastination: pragmatic case for meditation
It's still there, just used it to see if I had guessed right on Rachel's workings (I hadn't). Thanks for making a very useful tool!
Nice pivot to a strawman at the end there. UK could be demanding licenses for carrying cucumbers, it wouldn't affect his analogy.
BE: .Net minimal API, Entity Framework (SQLite or PG as database)
FE: React + Tailwind and few other libraries
It seems rather likely it was adapted from what was originally a racist meme format, but I doubt the author is aware of that or made a conscious decision to depict it like that. Memes often get adapted with so many edits that their original meaning vanishes. I'm glad we can plagiarize Stonetoss to make positive edits.
For the same reason the government hasn't broken up anything since Bell System in 1983: those 500 million that Google pays Mozilla is higher than FTC's entire yearly budget (430 million in 2023). It takes years to build a strong case, and companies can easily throw more resources at a problem than that. Monopolies don't even need to win the case, just drag the whole process on until the next election cycle, when all of a sudden the next administration is far less interested in following through. Rinse and repeat indefinitely.

Technically even Bell didn't lose a case, it broke up "voluntarily" before that happened.
Why is there always someone who needs to read things in like this where nothing exists?
Between jobs is the only time you touch LinkedIn, lest HR sees some activity on your profile and buckets you into a "actively job-searching" risk group.
>If Rust had a restricted subset which had a footprint compared to C

Take a look at "#![no_std]", a Rust feature.

If you do that, your Rust Hello World program will have 14 kiB (with no linker optimizations).

>and allows formal verification (including functional requirements)

See <https://rust-formal-methods.github.io/tools.html>.

Also, the Rust compiler can be used as a library and you can add whatever checks you want like that. See <https://yoric.github.io/post/uom.rs/> for an example (not used that much).

Also, I like <https://docs.rs/pre/latest/pre/attr.pre.html>. It allows you to define and then mandate specifying textual requirements (in addition to the usual conditionals).
"Don't put small inedible things inside edible things" doesn't sound like a bad rule to me, to be honest.
Pretty sure almost every tech YouTuber and definitely every tech website reviewed the Meta Quest 3 when it came out
It is. Here's an update from the same poster: https://x.com/fr3ino/status/1755876318560788784?s=20
Of course the system is not something that magically descended to the heavens, it is simply what people have agreed to go by. If it is unequal, it is so because the people have decided that they want it to be unequal.

No doubt because, as you point out, the typical person would rather spend their time making ends meet (i.e. pay for the luxuries of life) than the worry about making agreements with their neighbours day-in, day-out. You can technically survive on very little time commitment to "make ends meet". Just look at the homeless population. It is not a life you would want to live, but it could be done if you truly saw the need to assert your power. But, understandably, most people would rather focus on their personal goals and let the figurehead worry about the community problems.

What's the alternative? It's just people at the end of the day. There is no magic. Those who do the work are going to do the work the best way they know how. Even if they value your input and want nothing more than to work with you so that you can show your better way, they are not going to scour the globe to find you. If you don't put the effort in to make yourself known on a regular basis you will be forgotten about.
it's always better to have a product a few people love than something a lot of people like.
DataCamp is looking for a Java instructor with a strong background in software development/engineering to give an interactive, introductory online course.

Is someone here interested?
A fair point that programers mustn't do stupid stuff. But languages (and frameworks) can help a lot with that.

When a language (or framework) makes it easy to do the right thing, and hard to do the bad thing, a large category of "stupid stuff" is avoided.

I'm lazy, or tired, or stressed, or focused elsewhere. Make it so, that at these moments I'm forced to run extra miles to "do stupid stuff" and we've avoided several bugs (or code smells and such).

Like you say, that still leaves the domain logic to make mistakes in. But if we could make our mistakes only there, we've eliminated a lot of bugs too: we only have to pay extra close attention in a fraction of our codebase!

Now,we aren't there. Rust isn't, at least. There's still a lot of boilerplate or utility code where I can (and will) do stupid stuff. But rust, with it's proper defaults, secure by defaults, is a lot closer than most other languages. And rusts' emerging frameworks inherit that mindset and help us get closer even.
Python/Flask, HTMX, SQLite or Postgres, Bulma CSS.
I love vanilla Rails (that includes Hotwire) + Postgres + Heroku + Tailwind. I do often use Rubocop and some other rolling, and want to package that as a project starter kit.

I’m looking forward to seeing Rails 8 in action, as is going to make building PWAs easier.
I'm noting you are using this as an example

https://www.agenthub.dev/templates/hr_hiring/linkedin_profil...

LLMS are not capable of unbiased scoring, no matter how much you prompt them. Anyone using this would be vulnerable to anti discrimination lawsuits as it is trivially provable that the workflow indeed is biased.

And frankly, this is disgusting tech bro behavior. LLMs are incapable of grading without bias.

https://www.agenthub.dev/templates/education/automated_gradi...
Honestly I can’t remember half the dom manipulation stuff and at one point I did know it quite well. It’s just been 6 years since I worked on an app that wasn’t react.

It’s useless knowledge for most people now. Like knowing assembly.
Yes, exactly. And because all of this is bundled in laravel (and at some point I learned working with the framework), I'm using this since years for almost everything.
The hard part is usually not getting the component to look like the design but rather the fun process of discovering all the interactions nobody thought about while they were focused on pretty pictures
I don't think this article is very well-written. It gets confused about whether QUIC has a handshake or not (it does). And it conflates zero round-trip time with combining the TCP/TLS handshakes together.
This line is trotted out all the time... but her salary also was going up as revenues and earnings kept going up. From 2005 to 2022 revenues grew more than 10 fold, from 52M$ to 593M$.

https://en.wikipedia.org/wiki/Mozilla_Corporation
https://frankhecker.com/2020/08/13/mozillas-uncertain-future...

In recent years, the proportion coming from Google has also been coming down (even if slowly, from 90+% to just above 80%), and considerable cash reserves have been built up.

Her compensation is ahead of the median for companies in the 0.1-1 billion revenue range, but in line with the median CEO compensation for a company with 1-5 billion in revenues:

https://corpgov.law.harvard.edu/2021/10/07/ceo-and-executive...

https://corpgov.law.harvard.edu/wp-content/uploads/2021/09/F...

So if you accept that this is an unusually complex CEO role, then it does not seems disproportionate (when judged relative to the absurd disproportionate growth of CEO compensation overall).
There's a group of Italians who are well on their way to release a commercial Open Hardware PowerPC notebook, for all that's worth: https://www.powerpc-notebook.org/de/
> We shouldn't expect infinitely durable things to emulate tangible things that wear out because it would be convenient for rights holders if it were so.

Not only that, it's copyrights which are supposed to expire. The idea that physical media should be expected to degrade through the passage of time sooner than works will enter into the public domain is absurd.
I guess the cognitive dissonance is that I used to be able to say things to a coworker in-person which wasn’t recorded and tracked, using my voice. This was always a normal part of work, and I didn’t give it a second thought until it was gone. Nowadays it feels like someone is constantly standing over your shoulder whenever you’re at work, and there’s never a private moment. This is especially strange during holidays, since personal conversations tend to spontaneously happen around those times.

You’re right of course. I just wish we had something to fill the void that was left by in-person interactions vanishing. I think I’ll be doing WFH pretty much the rest of my life, and I absolutely hate going into an office in general, but there are definitely some aspects I miss. Being able to chat off the record with a coworker is one of them.
Nope. The binding is "one-way" in the sense that, when the component state (or props) change, the DOM is updated, but if the DOM changes, the component is not updated. Hooks are a pattern for declaring state, side effects, etc. but they don't materially change this relationship.
Will open source AI models will win in the knowledge industry? Not because it's good for business, but because censorship, both kinds think of the children and think of the corporates, hurts the performance. Open source models can be tuned without this BS. Finding a tradeoff between censoring and performance seems to be weighted towards the censorship more and more.
I was hoping that the Vision Pro would have camera access, so that developers could actually build interesting mixed reality/augmented reality apps. As soon as I saw that Apple locked down the cameras just like the Meta quest 3 I knew I'd be $3500 richer. Maybe one day...
Interesting perspective.

As someone who’s used GitLab, it always felt like he says - too much focus on random features that weren’t that interesting, while core functionalities that needed a bit of refinement got left in the dust.
> Finally, I'd like to share what I'm viewing with friends and family such as a movie screen or a 3D model fixed in the same position.

Within the Apple ecosystem and services, that’s what SharePlay is. This is already available on the Vision Pro.
TikTok and Temu pull cheap heaters after testing revealed fire risk
A cool way direct use Lisp in Python
I prototype a symbolic way directly using lisp like grammar in python, currently can define var, function, object etc, welcome to check and comment also look forward to work together on this project if you are interested about
Not really in the nordics (europe?)
As someone who has enough social interactions and friendships outside of work I am very happy with this attitude. My co-workers are not my friends and I'd like to keep it that way.

Indeed nowadays I have seen many articles publishing that it is even more prominent idea with Zoomers entering workforce and have a clear boundary between co-workers and personal outside-work friends. The companies actually do not like this because this means that those people have literally 0 loyalty to the company and only care for the money. Which is shocking, I know. \s
> It's almost as if the creator(s) built that site ironically.

No, the site's advice is simply more narrow and fine-grained than a blunt 'never use jquery'. From the front page:

> jQuery and its cousins are great, and by all means use them if it makes it easier to develop your application.

> If you're developing a library on the other hand, please take a moment to consider if you actually need jQuery as a dependency. Maybe you can include a few lines of utility code, and forgo the requirement.

This seems eminently reasonable to me. For a website, adding a jquery dependency costs little and you get much nicer, more maintainable code.

But for a library, every transitive dependency introduces the possibility of future version conflicts for applications that depend on it. And at the same time, library code shouldn't need to change and grow nearly as much as application code.

So library authors should strongly consider forsaking mere convenience for the sake of reducing dependency baggage. This isn't even JS-specific advice, it applies to most ecosystems.
Gardening leave is usually a term for a paid non-compete. I.e. you're not allowed to work in the same industry for 6 months, and you're paid salary for those months.
Just a little info, whenever youre in a Dutch city, the house numbers are numbered from the center. So you wanna go to the center of the city, you can use the numbers as orientation.
And about what it did in the past.

Because that built habits. Has large bodies of education and documentation around it, and often even tooling (like snippets, ai completion, linters, static analysis)
Front-end: A few static sites (i.e. landing page) + Angular.
Back-End: A few C# APIs with Redis for caching.
Database: MongoDB + SQL Server.
Deployment: Docker Containers on Azure via DevOps Pipelines (one-click deployment).
Clojure using for the server side https://github.com/kit-clj/kit

htmx for frontend, using the built-in kit htmx module.

Previously I used Clojure, re-frame and websockets using sente. It is very productive, but now I prefer the lightweight feeling of htmx.
This feels like some pseudo intellectual take. Choosing react for new projects is not “cargo culting”. It’s a proven and effective choice with a huge market to hire from.

Meanwhile whatever server side renderer of the week framework you pick could be old news and abandoned in 5 years.
knowing both i used to be frustrated by jsx's lack of support for plain if and for loops like razor has (eg map and the weird && syntax we general end up with)

eg
```
<ul>
@foreach(var item in list) {
<li>@item.name</li>
}
</ul>
```

of course this idea goes against jsx's implementation (as it's just nested functions) and paradigm of being html in plain javascript rather than an interpreted templating language.

some of the differences i really like (like being able to assign compoents to variables, pretty sure razor doesn't have anything like that).
I write this blog a while ago:

https://lolware.net/blog/react-xss-protection-cheat-sheet/

The feedback I got across the board was generally "what even is this code? If you it to work with react why isn't it a hook?"
Frontend:

- "vanilla" React (no Next.js or any other framework-y bloat)

- MUI

- React Router (v5 because v6 is a pain)

Backend:

- Node

- Typescript

- Express

- Prisma or Sequelize

- Sometimes Django/DRF in lieu of the above

- MySQL or Postgres

Deployment:

- KISS principle: one Digital Ocean droplet, no serverless or any of that
According to this random document I found on the internet [0], in section 7., QUIC implements a congestion control system similar to TCP New Reno.

[0] https://quicwg.org/base-drafts/rfc9002.html