skysight-inc/HackerNews huggingface dataset:
Yes, and I agree that it's always important to keep that possibility in mind. I am generally keenly aware of uncertainty normally shy away from bad bets (predictions).

But taken too far, that principle leads to abdicating our responsibilities as citizens in a democracy, so while I was definitely chastened by the experience I will kindly decline the invitation to shut up: I choose to get better instead. The sum total of my influence on this matter has been, at worst, to encourage quicker and more widespread adoption of home tests, which falls very short of pernicious.

I'm quite puzzled by P5fRxh5kUvp2th's vitriol - maybe he or she is ardently pro-mask? Since I alluded to my low opinion of mask mandates (which I stand behind), that could explain it.
Oh @dingosity, my favourite ex-cow-orker, I think you may be wrong on the bait-and-switch aspect. The third parties involved knew the implications of the GPL'd SL Viewer from the beginning. Maybe not everyone in the organization, but the people who agreed to buy a commercial license knew about it and it was supposedly budgeted for.

Though yes. If a company did do a bait and switch like that, it would be bad. But I don't think Linden did that in this case.
If they do the same thing, now it takes potentiality days of "phone tag" before you happen to find a time you're both free.

With async comms, you initially go back and forth over text/chat/email/whatever. Sometimes resolving in minutes/hours. If you both decide it'd be faster to chat synchronously, you schedule a call and do that.

Honestly, that fact async comms exist makes it kind of presumptuous to assume you can make someones device ring at anytime and just get their immediate and full attention. I feel that way both as a caller and callee.

There's obviously exceptions, such as immediate family: but we roughly know what each other are doing, and the context. If my wife actually phones me, I will drop whatever I'm doing because it's guaranteed to be more important.
There are Stable Diffusion notebooks out there that don't require GDrive access and run fine in Colab.
That's not a mis-communication by the employee.

There are several events that happen with refreshers/bonus:

1) Notification period
2) Granting period
3) Vesting period

When the notification period happens, the manager doesn't say "You are getting X units of stock". The compensation system actually at this point has zero idea how many units of stock you are getting. Instead you get told "you are getting $x worth of stock".

Then there's the granting period, in which those unvested stock units are actually granted to you.

This is important because there's a lag time between the notification period and the granting period. If your boss tells you you are getting $10k worth of stock and the stock price is $100 per share at the notification period, but is $105 per share at the granting period, you are granted 95-ish stock units instead of 100, because the number of stock units granted was based on the Dollar amount they communicated to you.
I think "OS" for "operating system" and "OSS" for "open source software" are quite standard.
This article is stupid.
There’s currently a problem in that there’s a sine wave demand curve. High demand during the day low at night. Electric cars HELP with this. Flattening the curve allows power companies to deploy stable (greener) energy sources without having to resort to as much natural gas to match the demand curve. A better headline should be “the solution to a current problem could potentially in ten years create the inverse problem”. That’s fine. Also, having your peak while the rest of the country has a trough is financially beneficial from a wholesale energy perspective.
Visualizing more than microscopes can show via computational nanoscoping
With any traditional ISA with wide registers and instructions, a.k.a. SIMD instructions, it is possible to implement the execution units with any width desired, regardless which is the architectural register and instruction width.

Obviously, it only makes sense for the width of the execution units to be a divisor of the architectural width, otherwise they would not be used efficiently.

Thus it is possible to choose various compromises between the cost and the performance of the execution units.

However, if the ISA specifies e.g. 32 512-bit registers, then even the cheapest implementation must include at least that amount of physical registers, even if the execution units may be much narrower.

What is new in the ARM SVE/SVE2 and which gives the name "Scalable" to that vector extension, is that here the register width is not fixed by the ISA, but it may be different between implementations.

Thus a cheap smartphone CPU may have 128-bit registers, while an expensive server CPU for scientific computation applications might have 1024-bit registers.

With SVE/SVE2, it is possible to write a program without knowing which will be the width of the registers on the target CPU.

Nevertheless, the scalability feature is not perfect, thus some programs may still be made faster if a certain register width is assumed before compilation, which may make them run slower than possible on a CPU that in fact has wider registers than assumed.
That's effectively a substack rather than a book though, and incentivises unfortunate habits (only providing morsels of information in each installment to encourage people to buy more, and dragging the book out).
A wizard is an interesting idea.

As for learning load testing, it's mostly medium-easy in terms of effort and understanding required; it requires a little bit of effort to know what you're doing. Also a bit of scientific common sense and maybe some knowledge of statistics helps.

I think any of these are probably good. https://www.amazon.com/s?k=jmeter

I read a Packt or Apress one that had more than enough on how to use it. I don't remember which one though.
The caption in the blog says this:

We’ve been all across the country and back trying to ID this man at his desk. Yes, that’s a Shriner’s certificate on the wall behind him. It was issued from the Sesostris Shrine located in Lincoln, NE. And his stationary says “Memo to Recorders.” The folks at the Lincoln Shrine have been very helpful to us be we still have not yet been able to ID this man.
Can you not simply remove the Pocket button, or install a different extension to keep track of sites for you?

iOS does not allow you to install an alternate browser engine.

Windows does not allow you to remove Edge.

That's very different from an extension or toolbar button that you can easily turn off or replace.
ARM's SVE is definitely interesting, but I do wonder if it is slowly be honing in on CRAY style vector processing. Which is definitely a cool idea, but a little different from the now-popular fixed-width SIMD. I don't know that it makes sense to call one ahead of the other yet -- ARM's documentation is clear that SVE2 doesn't replace NEON. "Mostly scalar but let's sprinkle in some SIMD" coding will probably always be with us (until ML somehow turns all programs into dot products I guess!)

RISC-V also has a variable length vector extension.
The issue is that Microsoft was using its market dominance to compel its OEM partners to include Internet Explorer and not include 3rd party browsers.

Apple is not forcing its OEM partners to exclude 3rd party browsers.

If Microsoft made its own hardware and packaged IE with its version of the OS sold on its hardware - there wouldn't be an issue.

The big difference is that Apple doesn't license its software to 3rd parties.

On the other hand, if Google were to compel its OEM partners to include software, then Google would likely be facing various government bodies that have issue with this process and possibly facing fines.
I can't really imagine how hollowing out a planet could work, but I suppose if you figured out a way to do it you could replace the iron core with superheated water or something similarly less dense than iron. That's why I also suggested just building a shell from scratch. It would effectively be a very tiny Dyson sphere.
I know there is bias in who enters data on levels, but is there something else that makes it garbage data? Can you elaborate? Because I have never seen it as 'garbage data' and would like to know more.
Thank you for all the valuable feedback. And thank you for the insight on how your team organizes a logbook. I'll try to expand on the process of the snippet organization itself when I have time for it (there's a newsletter on my website you may want to subscribe to).

Addressing the "fully self-sufficient program" - no, the imports are limited to minimum, at least from the owned codebase. 3rd party libraries are okay - the point is to limit the system coupling, and also to provide a fresh and unburdened look onto the functionality piece. Think github gists - you find them via google, they solve some pain point of yours, and they also serve as an "etude" for their authors.

After all, this development approach is a very psychological thing (and I would say, every approach is). It also aims to solve the issue of developer's burnout, the fear of an extremely big-scoped work, and gives possibility to ship as often as physically possible. Having a lot of snippets is way better than having something in development for weeks without any insight on what is being worked on. And when you've accumulated quite a lot of snippets, the task of gluing those together becomes a rather playful quasi-snippet in itself.

Speaking of the "framework-heavy" stuff, React included, - yes, it would definitely be harder to implement this strategy compared to, say, backend development, - you gotta have a lot of boilerplate just to make the snippet run (after all, it should be at least viewable in browser, which is already a lot.) But you still can use this way of development with a moderate success (and depending on your managerial skill or self-control): the front-end developer would have to accommodate and internalize the fact, that snippets are to be written with more boilerplate, and after all, React is component based, and components are already snippets per se.
Since a lot of services do integrations these days, I wonder are there some common connectors they are using?
Interesting! Any reason why they're specifically good for emulation?
The details are kind of boring and out of date.

We were repeated victims of minor property crimes. The police spent maybe 5-10 officer hours investigating, which is more than I expected.

However, they failed to run a (unusual for them, but legal) database search that would have almost certainly identified the culprits.

I think they would have done it if the crime was higher priority for them, but ultimately, they need to prioritize their resources on serious crimes and things that make for good public relations / internal politics (like if we were friends with the mayor or something).

As the victims, we had every incentive to pursue the investigation, but no legal ability to do so.

I'm well aware that our experience was far, far better than is typical in, say SF or Oakland. In our case, they probably would have made an arrest if we had a positive identification of the criminal.

That's not really the case everywhere, which is a separate issue.
Makes me wonder, could the GB/GBC hardware in the GBA be used by GBA games?
One of us is clearly confused. As far as I can tell, Apple does treat those bundled apps on MacOS exactly as they treat Safari. Any can be replaced, but all are good enough that most people don't bother. The most likely to be replaced is probably Safari (with Chrome).

Are you perhaps thinking of iOS?

Or are you trying to make some point I'm missing?
The article is referring this[0] video

[0]: https://youtu.be/nSvu9IDUjZw
While I agree with them about the blanket ban on alternative browser engines on iOS, when it comes to desktop, Microsoft did anti-competitive shenanigans back in the day too and yet Mozilla managed to still get a significant marketshare despite that.

Their secret at the time? Making an actually good browser that offered features the incumbent didn't have, something Mozilla has absolutely given up on in pursuit of making a Chrome lookalike, up to the point of removing certain features (that power users - their only marketshare at this point - very much miss) and even implementing arbitrary restrictions on the add-ons you can install on Android (you have to use a complex workaround to install unapproved ones). The thing is, people who want Chrome will just use the real thing and have no reason to use a slower lookalike with poor compatibility.

Here's an easy idea to sell Firefox on the desktop to the masses: built-in uBlock Origin, out of the box. Nobody I know that has tried an ad blocker ever switched back, and if they do fall for a dark pattern and switch back to an alternative browser, ads will be a persistent reminder telling them to go back to Firefox. Actually give non-technical users a real, tangible reason to use Firefox.
If the company supplies the hardware and software as a bundled unit, they are much more able to arbitrarily restrict and wall-in the device. It's just how the law works. This is how Apple seems to get away with a lot of super anti-competitive stuff that Microsoft simply could never with it's Windows OS (Microsoft being crucified for favoring IE being a prime example, while Apple blatantly does the same thing with Safari). That said, Microsoft can and does do all the same stuff on their Xbox or surface tablets, because in that case they do supply both the hardware and software. There's no "good" or "bad" company when it comes to this issue, as they both willing to do this in every scenario when they can get away with it.

Why it's structured this way, I've no idea. I don't think supplying the hardware should be the distinguishing factor that allows them to wall-in the device. It's one thing to force them to support and integrate devices/software into their product, which is probably not fair on the company, but it's another thing to actively get in the way. It's a thin line with a lot of grey area, but the way it's setup currently probably isn't right.
Hmm, unless the PRC can block transmissions from the Starlink satellites (or devote the resources to track down dishes in remote areas), I am not sure they can "censor" those connections?

I see your general point, though it seems to me to make a slightly-too-strong connection between the US Gov't and its policies and interests and Starlink's (that said, if the two were fundamentally at odds it doesn't seem like Starlink would be offering to provide access to Iranians...)
Yeah, this is mistaken. At my last job we deployed tons of c# on Linux. The .net ecosystem is a little complicated because of the slow convergence of its std library and runtime (.net core, .net standard, .net framework, .net), but as of a few years ago a bog-standard .net app did everything you’d expect on any computer.
Wow, this sounds very illegal in my state. I wonder if DRN even respects my state's laws about storing my personal information.
>Edit: I don't know how or why this is on the front page of HN. This seems like a super low traffic/low effort blog.

I agree, at the moment I'm writing this comment the post has only 8 points too. Isn't it a bit to low for the front page?
Oh, we are talking about the US here. Not Russia or China.
Why we moved from AWS RDS to Postgres in Kubernetes
This is how IEC 61131-3 is structured in automation vendor IDE's. Thanks to decades of brain damage many of the IDE's don't deal with textual source code but proprietary binary project files and you click to create POU's, progrm organizational units. Want to write a function? You have to click to create it as a POU and work on the code in a new window. In some IDE's the POU is even plit into a local variable window and a code window. Awful.

https://en.wikipedia.org/wiki/IEC_61131-3
Nope. We are all products of our culture. Our parents, our upbringing, education in school. Our friends. Our first experiences, and of course, the ideology that we have obtained during the process. The ideology mostly comes built into the society's culture, education and work life. So there is no such thing as 'ideologically neutral' or "I don't have an ideology". Its just that people think that the ideology that they have is 'normal', and they don't identify it as an ideology unless it conflicts with the incumbent ideology in the society.
A thorough search will show there are no published studies that reference it and replicate the results. If you seem to think it's been replicated and my queries have missed it, please link the study.
Pico8 is 128x18 res, so I think the maximum number of visibly unique lines you could draw from one point is 512. You can't even express sub-one-degree (sub-1.422222 really) rotations on Pico8 visually without subsampling etc.
> Many folks in crypto expected those Ethereum-mining GPU farms to just switch to some other GPU-minable cryptocurrencies.

This was a pretty common take but if you did the math Ethereum had about 90% of the GPU-mining market (by hashrate) so it was obvious the profitability was going to tank on those other currencies as soon as Ethereum switched.

In the long run yes, there will probably be another big spike in another cryptocurrency that starts another GPU boom. But it's not magic where one instantly springs up to absorb all the ethereum hardware at equivalent profitability.

A GPU crash was inevitable regardless of the interest rate drop hitting at the same time.
That is ridiculous. If secrecy means there is corruption then give me all your usernames and passwords. If you don't then you are corrupt.
Every company with algorithmic recommendations will run experiments to try to improve it according to various metrics. This is the well known knowledge in the industry, not a conspiracy theory.

Trying to improve peoples chance of getting a job as opposed to something lame like "engagement" is laudable. The key question is how big the difference between the groups. If the difference is marginal, then I think the knowledge justifies it. This will lead to more people getting jobs in the future, so the total utility increases. But if it was night and day, and they really fucked some people over, then it was unethical.
It's familiar scheme. It will do just fine when the mass couldn't resist hype, they will buy to help these early network stop burning cash. Fake it until you make it, while faking it needs a gigantic collective hype.
> is moving away

I think the citation would be for "is moving away" as that's the most bold claim.
Nah, Liveblocks.io + Slate is pretty far from Notion-like experience. It doesn't even do local undo/redo.
Apple starts manufacturing iPhone 14 in India in a shift away from China
It couldn't (besides the audio channels, which were shared).
If nobody cares where a Cessna is, why is it mandatory that everyone can find out? You could count on a fingerless glove the number of people who care where my car is, but I'd prefer not to stick that information in a public database. Some percentage of Cessna pilots prefer to keep that information private, and the rest can continue sharing that information regardless, so it would be a strictly positive-utility change. For what reason, other than the fact that Cessna pilots are a tiny minority, has this not been changed yet?
In 2022, I'm looking at the plethora of browsers available for MacOS, and sticking with Safari. Chrome would be my second choice, and in fact I have it installed, but only use it once a month or so on average. Nothing from Mozilla or Brave or anyone else is even installed.

You can say the complexity is required to compete, but I stick with Safari because it is simple, and fast, and doesn't gorge itself on system memory.
Why argumentum ad populum should be the ruling criteria for that?
It will be disconcerting, though maybe likely, that voters will not do a full sweep and put these politicians into retirement. Almost like the voters are comfortable in their cages.
The point I'm making is that if they treated their professionals the same way they treat iOS users, their professionals would no longer work with them.
I am utterly baffled that no response in this thread so far has taken issue with the statement "As you probably know intuitively, it won't work."

For me, this _does_ work and I have proven it many many times over the years by adding entire categories of technical knowledge to my repertoire. And not superficially, either - I get paid very well to do things professionally that I taught myself by reading Wikipedia.

If my experience were commonplace, the "it won't work" statement would be highly contentious in the comments here. Since it isn't, I guess I can deduce that I must be an outlier.
I don't have the hardware for it; what did you find?
Plastics. I think Plastics are going to be the biggest maintenance surprises in EV lifetimes.

We tend to think of plastics as "forever products" but most plastics are only truly guaranteed/rated for 15-20 years of active use. They just degrade in weird ways compared to other materials we expect to last. (And just being in a car dealing with all sorts of finger touches and all the jostle and motion of a moving vehicle can be quite "active use".)

My first car was an ICE I sold near its 15 year birthday. I severely under-utilize my cars, so it was still under 70K miles. The biggest push for me to sell and replace it was that the plastic knobs for its manual A/C controls had all started to break (and I was using pliers to adjust A/C, which is not fun, and quite dangerous while on the road), and even the manual window cranks were starting to have issues, and even the glove box was plastic and started to get real finicky about opening/closing.

Most EVs use touch screens and a lot of automatic controllers so there's fewer "common touch" plastics in an average EV than that first car I had, fewer manual knobs and cranks that can break, but there's still plenty of plastics holding up those touchscreens and in cup holders and other glove boxes/drawers/shelves/containers throughout the cabin interiors.

Most of that is "aesthetic" problems that don't truly impact the operation of the car, but as the user of the car you spend most of your time dealing with the cabin interior and problems with the cabin interior are easy to notice and easily become annoyances.

Cars aren't built to modularly replace the cabin interior (unlike some RVs which experience some of these same problems as they age but there's something of a market in refurbishing them every decade or so), so often the limits of cabin interior quality will be the "surprise" limits on car lifetime.

(ETA: Just to underscore, as my ICE example suggest, plastic degradation is not a new problem at all to cars, I just think that the circumstances that lead to it being a problem to me in ICE vehicle were unusual enough, because of low mileage. A high mileage ICE vehicle has a lot more problems to deal with before anyone even notices the plastics issues in the cabin interior. An EV even with high mileage may not have anywhere near as much in the way of serious maintenance problems, so plastics degradation may be the first maintenance issue some owners see/experience.)
I only see coarse thread offered in stainless, but there's a pretty nice selection of M8 x 20 set screws here (though now I realize, none with Torx drive, my bad): https://www.mcmaster.com/set-screws/thread-size~m8/length~20...
F# is not a windows language. It's been open source from the start and there are many compiler implementations that does not depend on Windows at all, like Fable.

That said I think it has many parallels with Rust and I enjoyed reading this comparison between the two https://github.com/Dhghomon/rust-fsharp

It shows how strikingly similar the two languages are, at least on the surface.