skysight-inc/HackerNews huggingface dataset:
I don't like this.

This reduces the scientist or designer to some small cog in the machinery, to the point where they are further alienated from their work.

Remove the scientist and replace them with an algorithm doing some poor facsimile of gradient descent for some protein energy metric. Or make it multiplayer where some crowd is doing the depth first search. No individual.

The only analogy I can think of is cooking. You can reduce all of the steps into a checklist, which can be optimized, but instinct is still the differentiating factor. Or rather, taste.

Maybe this helps designers develop taste better, but imo the interface is not the problem. It's training scientists to have better sense of taste or smell. There's a dimension above all of this that is still yet to be tapped.
Your assumptions about Linux are either all made up, or are based in working with some VERY incompetent people.

Most of what you refer to is Android is the UI stuff built on top of a slimmed down Linux Kernel.
I'd recommend you redo your prompt and also replace that hero image of the example chat because that is not how a human converses.
What would happen in the ideal world:

- All online messenger providers (Whatsapp, Signal, Telegram) e.g. withdraw from the UK market. Meta and Google gave a taste for this after Canadian link law.

- UK needs to come up with a crappy homebrew messenger ecosystem no one uses. Maybe a messenger.gov.uk?

- People download applications with privacy and sideload them to their mobile phones, keep going with their business as usual

- The number of childs protected or caught pedophiles stays unchanged

- UK parliament members who proposed the bill will look like idiots, not getting re-elected

- The "compliance" companies who promoted these solutions, as it's driven by commercial interest that guides the political discussion, go bankcrupt

However I remain doubtful if we have this ideal scenario.
>In regular threaded programming, cancellation is a bit more painful

No, it isn't. Nothing is stopping your threading library from implementing the same thing. It just turns out it is a bad idea to kill threads at random points in time because they may own things like locks. Or in the case of async await doing something that is thought to be atomic.
"This thing is bad"

"Then don't do the thing you disagree with? It's a free and open web"

"Why don't you start with agreeing with my position first?"
The entire goal of Starship is to carry human passengers.

Oceangate also started with unmanned test dives before they declared their submersible to be safe for humans.

It's not directly comparable. Oceangate didn't do that many test dives and never tested their sub to destruction, and SpaceX is working with several government agencies on certifying Starship (both Nasa and FAA). But there are parallels in attitudes that should be drawn and compensated for.
I feel like the incentives to participate in ordered society are diminishing every year. I just don't see the benefits anymore: if one doesn't fight, then they die meaninglessly anyway.
Given the context, it's assumed that "AI" will not be used merely for providing better search results, but for keeping people on Google.com with "original" answers.
The article also mentions environmental damage to nearby wetlands and a fire starting in a state park. Whilst immediate risk to life may have been low, the damage to the natural environment is very real.
On his private twitter? While NOT posting about the company at all?

It was a customer of the company that got offended. Should he know every customer of the company? If the company has 1000s of customers, are they all off limits? Are you supposed to know who they are?

If you work for AT&T and an AT&T customer (of the millions it has) is a jerk or you have some political disagreement with their views, do you get to tweet about it on your personal twitter account? Should they be able to complain and get you fired?
https://www.tohya.net/blog/index.html

It's mostly opinionpieces and reviews on videogames, but I occasionally publish programming related posts too.

- https://www.tohya.net/blog/programming/overthinking-web-app-...

- https://www.tohya.net/blog/videogames/the-evil-within-2-revi...

- https://www.tohya.net/blog/videogames/blasphemous-review.htm...
No, that was just regular idiocy.
It may be that risk control is one of the key factors in success. Either through diversification and a broad spread of investments, or having a defined loss per position and then having the discipline to sell. Position sizing is also important, not putting too much into one investment.
a lot of things

but also for a lot of use-cases a lot of things would be missing, be very bothersome

and most important a lot of the things you have left are semi use-less as they are all specific to one instance of hardware

but modern server applications are always spread across hardware (even if it's virtual hardware)
Sometimes the best decision is to turn around and walk away, and burn that bloody bridge behind. Better actually if that people will avoid you in the future.
Could you elaborate on the project? I'm curious
It wasn't work related, no? She wrote from the personal account, not from the @vmware or something.

I'm not pro insults on twitter. But I think much bigger problem than the insults is the way corporations try to claim everything as "work related". If that specific account or whole media (Twitter) had been explicitly mentioned as her job responsibilities, then I guess corporation was in the right, claiming that it was for work. But just trying to blanket control whole human lives during the employment period is bad. Bad for us, employees.
Obviously nobody should trade cryptocurrencies, but cryptocurrency exchanges tend to have unusually equitable market access for solo quants compared to US equities or whatever.
"Set-theoretic type theory" is working with the lattice of all subsets of possible values, where a "type" is one of these subsets. This lattice has plenty of structure, but sure individual subsets do not.

The category of sets is different from this lattice, since it allows arbitrary functions between sets for its morphisms rather than just inclusions.

"Set-theoretic types" have a meaningful notion of overlap. Usually types in other type system tend to be practically disjoint, like objects in a concrete category might be sets but the category itself doesn't give language to check whether the objects are disjoint sets.
What do you think would happen if perpetual longevity were achieved? I mean realistically, not ideally? I think it's almost certain we'd see those at the top become [even more] vainly obsessed with their own mortality to the point of doing absolutely every single thing they could, with no norms of behavior, to ensure no other human could ever, under any circumstance - no matter how remote, pose a possible threat to them.

You'd most likely have been born into society as something between a serf and a slave, with your life strictly by controlled to ensure you never might imperil the perpetuation of those who would almost certainly come to see themselves as Gods. And no, you wouldn't be immortal. That'd be too risky for the Gods. It'd be the absolute worst of humanity, frozen in time, due to the lack of death.

And oh boy, imagine the punishments they could contrive for anybody who might indeed imperil (or even deny) their utter supremacy. How about a million years of torture, if for no other reason than to use you (and the millions of others granted similar accommodation) as warnings to the rest of society? I can say, with at least as much confidence as you express about there being nothing after this life, that this life will end. But the thing I can add to this, is that that's also a very good thing for all of humanity to come.
Normally I'm not too cynical about politics (or most things), but in this case the policy was so obviously spectacularly bad that I find it hard to disagree.

And to be very clear: an extremely expensive short-term half-arsed fix that doesn't do a single thing to fix any systemic issues (and, in fact, will likely make them worse) is profoundly bad policy, no matter what you think about education policy in general. I was very disappointed at all people in favour of this, as it's just so obviously the wrong approach to fix anything as we'll be in the same (or worse) situation in 10 to 15 years.

Fix college tuition fees first. Then you can start doing something about the existing debt if you want.
What does the poor eyesight have to do with not being able to wear sunglasses?

There are prescription sunglasses for shortsightness, astigmatism, etc.

So the sunglasses-form VR would just have to cater for that. Apple's headset-form VR already does (offers the option to have prescription lenses in it).
It needs to align with the evolution of content consumption, which I'm sure it can. That's why i said (re)
> One advantage of async/await is that its easier to cancel things. For example, this leads to the design pattern where you have multiple futures and you want to select the one that finishes first and cancel the rest.

> In regular threaded programming, cancellation is a bit more painful as you need to have some type of cancellation token used each time the thread waits for something. This a) is more verbose and b) can lead to bugs where you forget to implement the cancellation logic.

Yeah of course Rust just makes cancellation so easy by allowing the Futures to be dropped. What about the resources these Futures could have allocated within the context that are not just memory? You are saying it as if async/await somehow solved the whole problem of stack unwinding.
Value investors pretty much do not use risk control as known from shorter term trading. They just buy low and sell when facts change (down) or prices change (up).
You are right that position sizing is important but for the opposite reason. Knowing your winners and then full on concentrating in them is statistically a big part of what makes successful winners.
How to Create a Postman Collection from Your Platformatic API
- Luck

- Get the best information, possibly insider

- Manipulate the market

- Not get caught doing these things

The strategies described in the article are strikingly similar to gambling advise. Applying these in a casino will minimize your chances of ending up broke, but you will still lose money in the long run, because of the house edge. I'd say it is the same thing with investment, if you follow these rules, you will mostly end up with reasonable market-rate returns. But to be really good, you don't just need a good betting strategy, you also need the house edge.
Admin burden is lack of docs and tooling to maintain stuff. You need to introspect and debug things and measure performance, manage logs, networking,etc... and there needs to be a pool of potential people that can do that job of maintaining it.

If you have an ngnix apk, it might need to talk to a php and mysql apk and a bunch of other apks and each of them have configs and require management. Essentially, my problem is that you would need to port everything servers now are doing to it but to what benefit? It makes more sense to import features you like in android/dalvik to gnu/linux. Less work/burden.
This is a great take. Added the book to my list
His talk on "Inventing on Principle" and Randy Pausch's "The Last Lecture" are two videos I recommend every student to watch.
Or how about this: we hold AI companies accountable for treating the internet as free real estate and attempting to put FOSS developer brains into a jar with a ChatGPT label. These LLMs should not be afforded the same rights as humans and should instead be treated as derivative works of their training data.
"This is the commonly accepted definition of open source and there’s very few who would consider your custom license open source."

You might think so but I disagree.
kill; e-commerce, in store payment terminals, online banking, all https, email, biometric passports etc.

It would be a return to the pre internet era, so probably is the will of the people and on form for the UK. I kind of hope they pass it then realise what it actually means.
> No engineer wants to be on the hook for a bunch of things cobbled together like this in production. How are you going to hire talent? How do you test the thing? Debug it? Logs? Analytics?

The point was that most of these things become less relevant when the surface area of the codebase gets smaller. Individual utilities are generally easier to understand, test and debug as separate units, logging is already baked into the system (syslog, anyone?), and why would you need analytics?
The failure of the flight safety system is a major screwup. I wouldn't want to be the person who has to talk to the FAA about it. Personally I'm not holding my breath for the next attempt.
>launching multiple apps in the same prefix

What's a "prefix" in this context?
Bulgaria Hosts Largest-Ever Digital Nomad Event, 700 Attendees from 40 Countries
I guess it pays to be temperamentful and "do nothing" if the pool of money you get to play with is huge to begin with. If you have limited funds to invest with, the temptation to take risk to make a significant profit looms large.
> or even something like Alpine Linux on the server directly (which some might actually consider, because of the simplicity and lightweight nature).

You are going to eventually run into the same issue most people trying to use Alpine Linux just because of simplicity and being lightweight run: musl is not a completely ABI-compatible seamless replacement to glibc and might cause issue with statically linked binaries, and other annoying issues you won't foresee.

Had this "pleasure" in the past in one of my infrastructure-heavy positions.
> Threads [...] are interfaces for parallel programming

Threads are both for parallelism and for concurrency. Threads have been used for decades on machines without hardware parallelism.

> are you telling me you never write a mutex or implement locking logic

aside from the fact that mutexes vs futures is completely orthogonal to async vs threads, I definitely prefer dealing with mutexes. 99% of mutex usage is trivial and deadlocks are relatively easy to debug. The issue with locks is their performance implicaitons.
> Don't just quit and let the amoral/immoral people win

If the opposite is stay and actually make efforts for change then yes. If it is staying and keeping your mouth shut then it's just keeping the status quo. And that may be fine and understandable but don't be offended when called out on that.
>> Premium subscription is just an antipattern of them removing options.

> It makes sense only if you believe everything on the internet should be free.

I wish HN readers would try and stay away from strawmen and address what others say.

If a product offers something and suddenly makes it product progressively inferior as a means to make a distinction of "this is premium", then it's an anti pattern. It feels scummy since it didn't start with "first X are free" and shows a lack of upfront monetization strategy.

>> YouTube music is in no way better than Spotify.

> I don't disagree. It's highly subjective.

It's highly objective if you actually use arguments, which you don't.

>> The benefits you site are possible without their premium, using other apps

> Piracy is always an option. But if you choose not to do it, buying premium makes sense.

Using the term piracy here is playing into the game of anti competitive companies who continually lobby governments to get their way over the actual desires of citizens.

You haven't really supported your quasi marketing campaign claims about the YouTube experience.

Truth is:
They had a product that was good.
Made it shitty and told you to pay if you want what you had.
You pay and laud it.

I mean, you do you but it's an unconvicing sell.
If you are forced to have "daily meetings with your manager" you might have spent the whole day drinking Jack Daniel's and planning a prompt exit :D
Are there any sources for this? I have a hard time believing that GNOME devs actively fight distros to make *checks note* gnome-boxes a required install on GNOME desktops.
It's also annoyingly opinionated in stupid ways. There's no supported way, for example, to adjust which services are enabled or not, and especially there's no concept of 'started but not autostarted', which can be important on a server (it's also obnoxious on the desktop as well, since it seems like a lot of the results for trying to fix this is people saying 'how do I stop snap slowing down boot').
We agree on the fact that it does spark conversation, I’m just not sure whether it’s the right kind of conversation for this place.
> crypto it is much harder to get away with it and leave with illicit funds in your pocket without getting caught

Ah of course, that’s why crypto neither attracts nor results in fraud or scams. Obviously, everyone who has tried has also been arrested and funds returned to the victims.

/s
The main problem with Snap is that it is user hostile (forced auto updates) and propertiary to some degree. Canonical is just up to some no good.

Containerization in general is aatter of taste.
Web servers should refuse requests for random, unnecessary URLs
>I wouldn't be surprised if electric vehicles have a much worse co2 footprint in its life cycle than your average 10 year old car

I'd bet they do. A lot of it is hand-waved away as externality.
>The investors who threw money at optics at the peak of the bubble probably would bankrupt us all if we ever hit a true “technological singularity.”

If we really hit technological singularity, that will be the hail Mary of all bubbles.
90% of for loops were generated by Ai? have they gone too far?
Charles Schwab company did a survey of those of their customers who did very well over the long run, and they found a surprising attribute of a large number of the most successful investors: they had forgotten that they had the account. Buy and hold!
Great, but it's ok to write it's not interesting too then?
The comment history for this account is mildly entertaining.
You can do `zfs set copies=2` for a ZFS dataset if you think there's value in the extra copies. That's better than a copy of the file because with a single bad block, the checksum will fail and ZFS will retrieve the data from the good block and repair both files. In practice, using disk mirrors is better than setting the copies property.
The issue is that they can't defeat encryption currently, and wish to.

Encryption can hide web browsing and a lot more, which they don't like.
The "no politics on HN" rule/convention died out around 2016 or so. Turns out even though Hacker News used to not believe in politics, politics believes in hackers. And everything about this story is actually about hackers, rather than a random political story like many highly-discussed articles as of late.
Concrete isn't waterproof, it might resist the flow of water, but as even most rocks are, there is at least a slow migration of water through the material.
Yeah, unfortunately important topics like these are typically flagged on HN and quickly disappear from the front page.

I understand why -- they tend to lead to flamewars. But I'm not sure if hiding issues like this is a good choice.

(Aside: I think it's telling that the apparent majority on HN is on Goliaths side in this case. Usually we're more on the side of the underdog. I wonder if that's just the latent misogyny showing, or if it's because OP is left leaning, or because of the pink homepage with the ponies.)
E-commerce will still happen, just with lessened security.
We just moved on.
> First, why should I even assume N is finite?

Our current understanding of physics dictates that the (observable) universe has a finite size and a finite lifespan, from which it logically follows that there can't be an infinite amount of humans.
You wouldn’t believe what you can get past a linter. You need test cases that cover the intention of the code, but I‘ve also seen well tested code behave totally counter to its purpose.
> These are extremely unpopular on HN.

idk.

HN just mainly complains about some implementation details.

Like flathub applications often not being sandboxed, yet.

Or Canonical forcing certain update strategies and similar on snap users.
> why does employer not say "dear whoever, this employee is clearly an idiot, and whatever they say on their private twitter does not represent our views"

Because:

1. It wasn't private, it was public and tagged the subject of the abuse directly.

2. "This employee" was on company time and actively representing the company at the time.

It doesn't matter what role you are, you are always at risk of getting fired if you embarrass your employer.
Did not hear back yet…
You can do exactly that with a Wordpress Docker container: install and run the container, it might even spin up a database for you if part of a docker-compose or you just rely on SQLite. The technical geeky aspect comes into making your blog available to the wider web through naming, you need to configure DNS, and serve requests.

I don't see how an Android app that you can "click and install" would help to configure your DNS entries.
To answer myself, it looks like mvsqlite operates as a VFS implementation, which means it works with pages, not rows. That should decouple size limits.
The point is that other solutions were able to use traditional threads or green threads (via stack switching) to solve the same problem without the compiler having to transform sequential code into a state machine under the hood (since pre-emptive threads can be suspended and continued at any time, and green threads at specific 'yield-points').

Javascript is limited by the single-threaded browser runtime, and the way that WebWorkers were bolted on later didn't help much because WebWorkers with message passing are too inflexible to implement even green-thread-style task switching.

The state-machine code-transformation was indeed the only way out of this dilemma.

Async/await is essentially high-level language syntax sugar and it shouldn't matter whether it is implemented via code-transformation, or with green-threads or real threads, or a combination of all those under the hood (but in reality it matters because there's a difference between 'code slices' being scheduled on the same thread or different threads when dealing with shared resources).
Sure does. Faraday stopped his EM experiments, not cuz of ignorant ppl, but "great" mathematicians of the day were mocking him for his lack of math skills. Without those experiments, no one
would have ever dreamt up electromagnetism. And on the flip side, "qualified" ppl who couldnt grok the math of Maxwell or Heaviside, would dismiss the math as just too complex. This type of stuff happens all the time. Social media amplifies it. But you just have to find good ppl and ignore the herd to make progress. And dont mistake capturing Attention on Social Media or HN for progress.
Async is, in many situations, better than traditional threads.

Threads are a resource hog. They take a lot of system resources, and so you usually want to have as few of them as possible. This is a problem for applications that could, in theory, support thousands of concurrent connections, if not more. With a basic thread-based model, you need 1 thread per connection, and if you have long-lived connections with infrequent traffic, those threads mostly do nothing but consume precious system resources. When you're waiting for data, the thread is blocked and does nothing. With async/await, you can have far fewer threads, maybe even just one, and handle blocking through a system call that wakes a thread up whenever any one of the currently blocked tasks is ready to progress. In languages with much lighter thread alternatives, such as Go's goroutines or Erlang's Beam processes, this problem basically doesn't exist, and so those languages don't need async/await at all.