ikurei

That's a good point. I didn't mean to demean React developers: I've been one for years and I can't say I optimized everything I could've.

The blame for not caring enough about performance and UX is on the whole industry. That does include developers, but not just them.

I don't think that is fundamentally broken. React is just not the right technology for a single button, and it's not trying to be.

If you tried to use photolitography (the technology used to print the circuits in microprocessors) to do tattoos... well it could probably work, but it would be highly inefficient and expensive and bad.

React is for complex web applications, and it I don't think it's a very valid criticism to say that it is bad for a different use case. To some extent, the React community may have over-promoted React as the final web-dev framework, but that's also a mistake.

In any case, kudos on creating Nue, looks really cool, I'll keep an eye on it ;)

I'm not happy about how bloated most React sites are, and I've mostly stopped using it unless clients specifically request it after years of it being my main framework, but...

> The issue is that these huge frameworks have made the web a horrible slow mess.

I don't think this is accurate. Most bloat in the web is caused by:

a) developers don't taking any time to optimize, lazy load, cache, minimize dependencies...

(This is partly on React, or may be on the culture around React that has made all of this normal and acceptable.)

b) the 300 tracking scripts every site has to try to squeeze as much revenue as possible

(I remember being shocked, some years ago, when I saw a site with 50 trackers. May be it was The Verge? Or some newspaper? Now I don't even bat an eye when the number is in the hundreds.)

React sites can be extremely fast if the developer cares, and the bloat it introduces is rarely relevant. The OP article describes a button as 78K, but that's because it's loading the whole of react for just a button.

If your page has hundreds of buttons, you don't bring 78K hundreds of times, and so complex sites built with React are not that inefficient.

As a Devops engineer, do you have stats on how much of that slowness is the framework or the actual app code?

Because their argument, in which they do have faith, is that a cacophony of disagreeing viewpoints casting doubts on the common national project is hurtful, even if those doubts are unfounded and those viewpoints unsubstantiated.

I'm not defending autoritarianism or communism, but I think you're just not putting yourself in their shoes and looking at things from their POV. They supress other viewpoints not because they're afraid to be shown wrong, but because they believe it's best to supress them and not have people confused by enemy missinformation.

(Not an expert, but this is my impression from talking to both chinese and vietnamese people who defend or at least don't oppose their communist governments, and also spanish autoritarians who defend the Francoist regime. I used to think they were brainwashed/dumb/evil, and now I think their worldview makes a bit of sense, even if it's still misguided.)

Thanks a lot for your answer!

How about the database? You're just using IndexedDB for the persistence? How was the experience of working with it?

Congrats on shipping! I'll try it out on my next freelancing project.

I love this approach of local-first webapp, with optional sync afterwards. I've been working on a journaling/note-taking app with a similar approach, but finishing pet projects on limited free time is hard.

Could you share a bit more about the stack and your experience building it? What was challenging?

I have one and my main gripe with it is how large the power brick is. It's practically like carrying a second mini pc; I didn't take this into account when I got it, lesson learned.

The map doesn't go that close to the present.

"Northern" was added to the name in 2019, before it was just Republic of Macedonia.

> "The Prespa agreement of June 2018 saw the country change its name to the "Republic of North Macedonia" eight months later." - https://en.wikipedia.org/wiki/North_Macedonia

Yes.

https://news.ycombinator.com/item?id=42363727 - Itch.io Taken Down by Funko

You mean tablet? Has that ever been done, having the tablet provide both power AND monitor to an external computer?

Sounds a bit odd to me, specially considering the tablet is already a full computer.

I love this form factor for its nostalgia, and because it's just cute, but it's wrong for almost all use cases.

> Gambling was already an issue 100 years ago, when we were closer to God, allegedly. "God" and religion also aren't particularly interested in gambling

No doubt it was. Workers were alienated before the industrial revolution too, and we were already emitting CO2 before the 1950s, but the scale of the problem changed in a very impactful way.

Of course I doubt we can get reliable statistics from 1920s, but I don't think you should disregard their argument just because it was happening before. Gambling is as old as numbers, and it's not going to go away, but we can still look for the factors that drastically increased the magnitude of the issue.

Out of curiosity, what culture are you referring to? I've known a few individuals trying to do such changes, but no wider culture.

> There's a lot to be said about the "old school" way of movie rentals.

Please do say it! I'm old enough to remember VHS and video clubs, but may be not old enough to have a lot of nostalgia about it.

I can't think of what was better then. Sometimes you'd get a kind and knowledgeable video club owner who'd made fantastic recommendations, but more often than not it was an underpayed kid who just wanted to go home.

May be people used to take watching a move more seriously, and therefore enjoy it more, when the process was more involved and you didn't have millions of movies and shows a few clicks away, but does that count as an advantage?

> We're now paying and exponential amount of money for the same level of entertainment.

This was certainly not true where I lived. The ammount of movies and shows that get watched in an average household these days would bankrupt the family in the 90s.

There are more options. Many medications are usually prescribed together with other meds, to help with the side effects. We may adjust the formulations, or learn what to compliment it with.

In and of itself, the product might be a decent MVP to validate the idea or some aspects of the design.

The problem is in how they've marketed. If you're taking people's money and giving them an MVP, you need to be upfront about it; if you aren't you're doing a bad thing.

I appreciate it too, and they're of course going to call it "open weights", but I reckon we (the technically informed public) should call it "weights-available".

I'm curious, when do you need this?

I still use `writeFileSync` and such out of habit, but I don't think I really need them since we got first-level await (out of async functions).

There was a time I was writing scripts using Node about once a week, and I settled on ShellJS. I don't remember loving the experience.

Haven't had this need in at least a year though. From looking on npmtrends[0], ShellJS still seems the incumbent and quite alive.

Are these new zx/dax/bun-shell tools, each inspired in the previous one, way better?

[0]: https://npmtrends.com/dax-vs-shelljs-vs-zx

What happens if you pick Dax and a year later it's Bun-shell that emerges as "the winner"?

If you stick to Python until a winner emerges, how does that help you? You'd have some old scripts in python, and some new ones in WinnerJS, which I think it's worse than having some in WinnerJS and some in LoserJS.

Your LoserJS scripts won't stop working. At least Bun-shell and Dax scripts in the same language. Since Bun's got some inspiration from Dax, I'm sure the API won't be that different.

I'm usually not one to jump on new JS stuff, but writing scripts on any of these feels relatively low risk.

Also, I'm still maintaining code that uses the ORM-that-lost, and the Dates-library-we-don't-use-anymore, and it's OK.

I've been wanting something like this recently.

I want to occasionally have my "virtual computer" with me to use on other hardware. (ie my SO's laptop, my Steam Deck; hardware I mostly trust). I find myself bringing my laptop many places where I don't actually plan to use it, just in case some server goes down or the like.

Why Qemu though? Why not a Live USB? Is it just for the ease of treating the VM as a regular file for backup and transfers? I have little experience with Qemu.

I don't think the assumption is you'd be doing that all the time. It's just good that you can do it if needed. If my laptop is stolen, I can just buy any linux-compatible laptop and run this, or I can borrow someone else's if I judge the risk acceptable.

From the article:

> When I switch from my work computer to my personal computer I just bring the USB stick with me; same thing next time I upgrade a computer.

I love named parameters. Whenever I use Python or Swift, I hate having to come back to languages like C or Javascript that don't have them.

It just seems like such a clear win to me, that and writing long numbers like 1_000_000. So much more readable.

Why aren't these features more common? I'm a bit surprised Typescript never added them. Are they too difficult to implement in compilers/interpreters? Do they cause too many issues for interop?

I'm honestly curious. Is it just that not that many people find these features appealing?

PD: I know you can emulate named parameters using objects in JS/TS. I don't love the performance consequences of this; it's good in some situations, but terrible in others.

It may not be right for you, but I can see situations where this would be preferable.

If because of your job you find yourself doing these operations very often, and the ability to do them from several devices with different OSes is valuable, it might be great to throw this on a server.

Or if your work has several people, may be not very technical folks, do them often. I’ve worked in a couple of places where this could’ve come in handy.

Also, it includes an API. Also, being open source, if in the future you’re creating a web app that needs some of these features, you could learn from/copy from its code.

I think this is a good contribution to the world.

> I don't understand what is the point of bloating softwares like this. Not even speaking of the very bad consequences for the planet.

I partially share this concern. I wouldn’t deploy this for myself unless I had a very easy way to stop it and start it, but anyway while not in use it it should only be consuming a bit of RAM, and there’s plenty of very efficient hardware suitable for small servers these days.

I love that you went there with an invasion force (not judging) but also helped local medical infrastructure.

The Non-Men from Prince of Nothing are more or less elf-equivalent, and I thought it gives a much darker and more interesting interpretation on the impact that immortality and tremendous historic loss can have on such a race.

However, I reckon the only reason these dynamics seem bizarre is that they would be very bizarre for humans, but elves are definitely not humans; their nature could potentially be very different, especially in LOTR where they have an infinite lifespan and a very different creation than other peoples.

Elves are basically aliens, however human-like they look. Would it be strange to find such dynamics in an alien species of octopus-shaped creatures that communicate through electromagnetic fields?

So many laws go against human nature; those might be the most important laws.

I don't expect the greedy and powerful to change, but as a society we should do more to protect whistleblowers, the same way we protect threatened witnesses.

Also, more solidarity between workers, although not always possible, would go a long way. So many Google employees can definitely afford to quit in solidarity, or strike. Not saying it's easy, I recognize it isn't.

Since you mentioned this, what would you say would be the right Lisp for more pragmatic, cynical reasons?

What Lisp should we learn if we want to make money from it?

Could you please elaborate on the security implications?

This is, IMHO, a very weak argument.

"Applying your principles to these hypothetical situations might lead to a situation you, western consequentialist, would feel is abhorrent."

Yeah, we all know our feelings and intutions about what is right and wrong, and our reasonings, may not always match. Who hasn't felt guilt, or at least unease, about hurting someone you love, even though you knew it was for the best?

This is basically saying:

"Your best effort to reason a moral code from first principles doesn't match modern western moral intuitions about justice"

That's no challenge for consequentalism. It might be a challenging decision for someone trying to implement a justice system, but all justice systems are full of weird compromises and grey areas.

He kinda explains it later:

> I think that inflicting suffering on vicious wrong-doers is morally praiseworthy even in the absence of any deterrent effect. Deterrence is a happy byproduct, but the fundamental point of punishment is to balance the scales of justice. In my Hitler-on-an-island thought experiment, for example, I maintain that the morally correct action is to make Hitler suffer as much as possible. Though you can’t make him die twenty million times, you should try your best to approach that ideal.

However, something is off here. They don't so much think that punishing wrong-doers is right; I suspect, since no reasoning is given, that they feel it's right. I'm no better, I don't agree with redistributism just because I don't feel the same, but I do feel that suffering is bad.