skysight-inc/HackerNews huggingface dataset:
Synchrotron radiation is electromagnetic radiation emitted by radially accelerating charged particles. In this experiment, there are no such particles. In a blackhole, there might be, but we are very far away from doing such precise measurements on blackholes.
I quit all social media, facebook possibly 6 years ago and the others gradually after that. I haven't had or watched a TV probably in 10 years. I use whatsapp right now to communicate with a handful of friends and family and github for work and open source. My apartment also doesn't have an internet connection so no netflix/youtube whatever. I tether my phone with JS and images disabled every nown then to read HN, send a few emails, download some docs or packages and thats about it. All of this happened over a long period of time so I can't tell if I feel better than before but I definately have plenty of time to read and cook. A bonus is I've also become less reliant on search engines / stack overflow to program.
https://github.com/tc39/proposal-bigint is shipping in v8 (chrome and node) and firefox is about to ship
I don’t think the author has the causality correct here, at least for biosciences. The statistical problems existed long before omics, big data, etc.

Most of the graduate programs don’t require students to take statistics, or if they do, it’s very cursory. Furthermore, students often learn very little about assay design - they end up thinking that non-linear responses are linear and do things like divide assay signals to get ratios (two sins here: assuming the assay response intercepts at 0 and that it’s linear).

So at least for the biosciences, it’s been a shitshow for a while.
Facebook definitely does not. I got an ad to join a Facebook group for bisexuals despite not having any information on my profile or in my post history to that effect.
This isn't code abstraction, just splitting up long functions. Obviously if you name your split functions "foo" and "bar" then it hampers legibility. But if you name them "doC" and "doBCD" then you can read them fine.
Null coalescing is already possible with ||.
Though I'd like ?? If it worked for undefined coalescing as well.
Can someone explain a bit what’s happening around the division?
https://github.com/westerndigitalcorporation/swerv_eh1/blob/...

Or give me some google keywords? Is there a link with the pentium bug?
Absolutely this. I've done work in both Swift and JS (well, Typescript) and every feature on my wishlist is from Swift. Null operator like you suggest, guard statements and structs, which are the best equivalent to value-type objects as outlined in the article.
It would be cool to see the cells checked as well. To someone unfamiliar with BFS, the demo makes it seem like the process of finding the solution doesn't involve exploring any other tiles than the solution itself.
Surely that sewage pump operator obtained a permit to block the street that day?
What about those "other two colleagues"? They weren't further mentioned; were they perhaps a made-up excuse?
Isn't this the exact concept of those running blades used by paraathletes?

https://en.m.wikipedia.org/wiki/Flex-Foot_Cheetah

These use carbon fibre and if I recall correctly are proved to be a more efficient tool for running competitions than natural legs. There is debate if it should be allowed on regular competitions or if it counts as "doping".

A similar design adapted to able-bodied people might be a better solution than his metal structure design.

I think this is the downside of working solo and focusing solely on registering patents and getting rich. You miss how other people contributions could improve your product.
Working over 40 hours a week is bad for work-life balance, as the employee won't have enough time to spend his money, but it's a lie that it decreases productivity. The most productive people that I know work more than 40 hours, and I don't think they do it just because they are lazy / stupid.
I think this is an interesting example of having intrinsic motivation driving the extension of the work. Perhaps being requested to do so has a different effect on performance
This is why it's so important to divorce self worth from achievements. Everyone cannot possibly win everything.
I suspect it's an issue of (observed) frequency; many people at least believe that the overwhelming majority of unions do more harm than good. I have nowhere near enough experience to say whether this is true, a misconception, or blatant propaganda, but it is a sentiment that I have observed.
They also inherit break/continue/yield/await/return/etc, which an iife will cut off.
Simplicity and elegance
A lot of great and well-thought-out suggestions here. Whenever taking deeper dives into Javascript, I tend to find myself on 2ality.com though google searches and whatnot. They do well when it comes to breaking down the language and features.

I'm a fan of 2.2: destructuring switch, although I occasionally employ something similar in JavaScript and other languages with a `switch` statement:

const resource = await fetch(jsonService);
switch (true) {
case resource.status === 200:
console.log(`size is ${resource.headers['Content-Length']}`);
break;

case resource.status === 404:
console.log('JSON not found');
break;

case resource.status >= 400:
throw new RequestError(res);
break;

}

It's missing the destructuring aspect, so the first case is a bit more verbose, and I imagine there's better potential to optimize something like the OP's example. But it has a similar effect to the example and works today.

Slightly related: I really wish `case` worked with brackets instead of break, similar to OP's example. It looks cleaner and is easier to visually parse. I suppose that's only better if you prefer brackets (which I do).
You still have to be more verbose, though. You can't do obj1?.obj2 with ||, not could you do obj1?.method()
Exactly, it forces people to present their life in tiny little stories that are transparent and gratifying at a glance, and they constantly attend to that perspective on their life.

In a time when everybody had a certain number of friends, some closer than others, you could recognize that some of your friends were shallow and influencing you to have a shallow perspective on yourself, and you could keep those friends at a distance while seeking closeness with friends that had a better influence on you. Now everybody has those shallow friends with them all the time, even when they're alone. Morning, noon, night, taking a bath, sitting in a cafe with a coffee, looking at art in a gallery, going for a walk alone, the question in the back of your mind is always, "How do I present this moment to someone who will grant two seconds of attention to it, and who doesn't know me at all?"
They also have the most dev friendly fees I've seen. You're only obligated to pay credit card fees, beyond that is a voluntary percent of sales you can give to Itch (set at 10% by default.
anecdotal evidence in the United States, in the last twenty years.. the concept of "overtime" has been crushed out of existance.. tech workers are essentially expected to respond to signals and/or work, just about all of the time; certain contract-bound jobs are "milking" overtime to get pay raises that are otherwise not available; employers offer extra shifts and hours to existing employees rather than hire, even if there is too much work.

It seems naive to see these one-line comments calling for 35 hours or less, when the actual-fact on the ground is extremely the opposite in a large number of cases.
People are definitely depressed, especially relative to how things should be. You don't see it much on hacker news, but you do on other forums. 20 year olds who are relatively well educated who see no future.

I don't want to take anything away from you. If you are enjoying your job and your life, that is truly great. But I would encourage you to take care of your future. Make sure you have progression, or something else, to show for it. You wouldn't be the first one to change perspective when life, or work, changes.
Induction is the most important principle for proving properties of programs.

The principle of Actor induction is:

1. Suppose that an Actor x has property P when it is created.

2. Further suppose that if x has property P when it receives a communication,
then it has property P when it has processed the communication.

3. Then x always has the property P.
You don't need it to switch on and off 1000s of times a second (is that what you're referring to?) you need it to switch fast enough that it could do that though. If it takes too long you would get brown outs and surges.
There will probably always be a snarky, jejune dismissal in every JavaScript thread, but commenters should think to themselves, “It doesn't have to be me.”
A reference implementation in a purely functional language.
Get a rubber ducky. It's not a person, but then again, I meet very few people who know enough about what I'm working on that they're helpful in giving advice, so they might as well be a rubber ducky.
This weirdly seems like the "right" implementation to me. Somehow I feel like a TTY generally doesn't need or deserve to know when keys are pressed and released.

That said, is there a more end-to-end summary out there of how keyboard input is handled in GNU/Linux? I have the vague understanding that USB HID scancodes are translated into keycodes, which are sent along to X applications or a TTY, but where and how each step happens is still a bit mysterious to me.
Needs more punctuation. I don’t know about the rest of y’all but I get disappointed when I look at JavaScript and it’s not awash in a sea of angle brackets.

But seriously, be careful not to ruin it with too much “I need this!”
Is this even news? This has been common practice for 10+ years in online lead generation businesses. I'm sure it's roots extend further back than even that...
This will be an interesting book to read... also showcasing multiple maze generation algorithms: https://pragprog.com/book/jbmaze/mazes-for-programmers
I will never understand why push notification permission wasn't put behind click activation like many others are. The span of that permission prompt is very annoying.
Teichtechnik, Teichzubehör and Teichbedarf Kaufen – Manzke Teichtechnik
This link compares search volume for Scala, Rust, and Kotlin for past 12 months in U.S.

https://trends.google.com/trends/explore?geo=US&q=%2Fm%2F091...

(Scala wins by a large margin!)

Awhile ago I chose Scala for a multi-year side project. I love writing Scala. I think the Scala community is quietly productive and mostly talks to themselves.

I'm not a Scala expert by any means, but I have have been programming for awhile and appreciate the power and terseness that comes out of my Scala code. It feels like I have more time to design well because I needn't write so much code :P.

Going to attempt a good/bad/ugly for Scala...

Good:
- Scala ecosystem very much under active development. Scala 3.0, compilation speed improvements, popular libraries updated regularly, IDE integration (VSC is recommended right now I think)
- Powerful. Scala's type system is relatively advanced. If used properly I think this can reduce bugs and cost of maintenance and new features.
- Fast and portable. jvm!

Bad:
- Scala's relatively slow compilation reduces cycle time, but I find often this is mitigated by confidence in the code I'm writing, so I don't often need to stop and run it to ensure correctness.
- Very high learning curve to wield the power effectively. Scala is an ecosystem that demands commitment. For example, sometimes I feel like I'm missing the requisite PhD to get the sbt build tool working properly.

Ugly:
- Due to Scala's power and high learning curve, a few failure modes may occur that make Scala impractical for many real-world software teams: Scala/functional experts can write a "Russian doll" of abstractions that's hard for someone less experienced to decipher, code review, or maintain; new team members who are also new to Scala/functional may have to ramp up with both business/codebase and functional concepts; and Scala gives you so many different "ways" to solve the same problem that code styles may diverge even in a small team, increasing cost and risk.

Overall I really love Scala, am looking forward to Scala 3.0, and intend to use it for many years, especially for projects with small, experienced teams where Scala's power and learning curve is an asset and not a liability.
When it works, this is good advice. Unfortunately, not everyone is in a position where they can reasonably make that kind of decision; someone with (say college) debt in an area with a terrible job market realistically has very little choice.
I work 40 hours a week, give or take a bit here and there. I know startups and some bigger companies expect more, but I've never worked for one. I don't think I ever will if I can avoid it. I feel like companies asking their workers (and I'm thinking of software devs) are abusing their position.
If they don't budget it, then is shows that they don't care about parking tickets at all, they just pay whatever. Budgeting it shows they are tracking tickets which is a necessary component of reducing ticket counts.

Rhetoric is fun; it's easy to prove both a proposition and its opposite.
I like these pieces for tempering the hype around driverless cars.

But it's also true it is still early and the technology will improve.

I personally don't believe it will become as reliable as people think. The last percent are always the hardest — but to make a driverless car better than a human, they're crucial.

But who cares what I (or others) think? We shall find out the truth of the matter soon enough. I just hope whoever mispredicted will take a note of it and keep that in mind the next time they make a prediction.
Human translation: https://www.reddit.com/r/wow/comments/akbdug/only_when_mats_...
Try Kotlin
Even that is not really comparable. The WMF does not actually have any members, and only has a superficial pseudo democratic shim (if that is good or bad is a different discussion though).

The "alarm" is caused because concerted action of roughly 10% of the OSMF membership could easily tip the current wobbly balance one way or the other, and there is no guarantee that the current "hands-off, low budget approach of the OSMF would survive such an upheaval.
Couldn't help but wonder what role the union played in the recent GM plant harassment case.

They're gonna hang a noose and GM is still too scared/unable to fire them? Am I misreading this?

But also can easily also see how merit based promotion at a production plant would be used to work workers to the bone. Gotta be some kind of balance.
Check any dictionary, except a 2000 year old Latin one. A tyrant is “a cruel and oppressive ruler” (Oxford American). Since you know that this is how the word has been commonly used for at least decades, and it is entirely clear from context that it was the intended meaning here, why do you feel it appropriate to waste everyone’s time with such a transparently bad-faith attempt to derail the discussion?

Then, maybe, actually engage with the argument, instead of just restating its opposite without adding anything to support that viewpoint.
SQL parsers, like postgres and mysql.
But on the other hand Arduino is still doing just fine for non-networked projects, so it's not all just comically oversized hammers.
You are still blaming the laborer for management's policies re (not) allocating sufficient time for correct work.
Perhaps. At least they’re not burning California to the ground.
UK could ban social media companies over self-harm content
In a lot of places this is an implicit rather than an explicit expectation, which makes it more culturally acceptable. It can also be “optional” in the sense that you won’t get fired for underperformance if you don’t put in extra hours, but if you want a bonus/raise/promotion (or to be protected from the next round of layoffs) you need to “demonstrate your dedication” with presenteeism.
The news response from supermarket chains where I live is that individually packaged fruit and vegetables helps reduce supply chain food waste.

Makes sense (e.g. one squashed tomato during transport will only waste one package) - no idea if it is true though.
There's also the whole "jumping stilts" category that appears to have peaked few years ago and now subsided to almost zero.

https://en.wikipedia.org/wiki/Jumping_stilts
Indeed, there is nothing new about this issue at all. It was even one of the arguments used in the Constitutional Convention as to why the new American government needed to be much less democratic than it ended up being.

> Mr. GERRY. The evils we experience flow from the excess of democracy. The people do not want virtue, but are the dupes of pretended patriots. In Massts. it had been fully confirmed by experience that they are daily misled into the most baneful measures and opinions by the false reports circulated by designing men, and which no one on the spot can refute. One principal evil arises from the want of due provision for those employed in the administration of Governmt. It would seem to be a maxim of democracy to starve the public servants. He mentioned the popular clamour in Massts. for the reduction of salaries and the attack made on that of the Govr. though secured by the spirit of the Constitution itself. He had he said been too republican heretofore: he was still however republican, but had been taught by experience the danger of the levilling spirit.

http://avalon.law.yale.edu/18th_century/debates_531.asp

Outright propaganda, foreign 'interference', and yellow journalism were extremely common in the era that the Constitution and the Bill of Rights were created! The media of the day was substantially less centralized, even a medium-sized town had multiple newspapers, and political pamphlets of all natures were common.

Complaints that the people are voting 'wrong' because they're misinformed by 'designing men' are absolutely nothing new and date back to our earliest democracies. Really, the only interesting part is that the complainants are almost always defending entrenched, powerful interests. In American history, it has always been populist and/or socialist movements decried as the result of a woefully misinformed populace, and it was always analogous movements in e.g., Athens and Rome (the Gracchi, for example.) Propaganda supporting the entrenched rich and powerful and their policies is, somehow, never seen as an issue.

Going back again to the early years of America, the hysteria about 'propaganda' led to the passage of the Alien and Sedition Acts, which were used to suppress the Democratic-Republicans and their press outlets...which ended with the Federalists being crushed in the 1800 election. When I hear complaints about propaganda in democracies, what I hear is the complaints of the rich and powerful that the common people might be voting in their own interest, instead of those of the rich and powerful.
> Though he’d spent a small fortune securing international patents, Seymour didn’t have the means to fight infringements.

Wouldn't lawyers take the case on a commission basis? (I just learned it's called "contingency fee")
It’s true, but some of the most un-productive people I know also work a lot more than 40 hours. If anything it feels like no correlation to hours working.
This is very nice, clean and to the point, I really enjoyed it. I was looking for articles similar to this as an inspiration for a series I want to write shortly. This is definitely bookmarked.

For more context, we're working on Solo, which is an open source security key. The firmware is currently C and we're working on a Rust port. There's no wifi. BUT, and here comes the interesting part I think, there's Webauthn. Browsers already have an interface to talk to the security key via usb (soon also nfc), and this interface supports extensions.

This means you can write js applications that interact with the security key with no need for a server/api on the key itself. And of course, by modifying the firmware you can support additional features. There's already code for blink, digital signature, user input (pressing the button), so it shouldn't be hard to copy & paste.

Anyway, great post, thank you for sharing.
This? https://en.m.wikipedia.org/wiki/Pentium_FDIV_bug

Edit: This is just the top result from https://duckduckgo.com/?q=pentium+cpu+bug
I think it is worth it to learn the functional aspects. Depending on other things you would want to explore there are some great libraries - Building reactive systems with Akka or data analysis/pipelines with Spark. I would suggest looking at a few books to get going with Scala as online resources aren't great.

- Functional Programming in Scala

- Akka In Action
I write my wiki and stay in touch with people over it. It is my lifetool. I try to own data and my identity. I integrate communications by hand into my wiki. I write detailed letters to people that mean something to me now. I'm more social than I've been in a long time this way. I get to talk to people who demonstrate they care, and I have evidence that they do.

https://philosopher.life/#Find%20The%20Others:%5B%5BFind%20T...

Hey, you should contact me. We can talk about it!
Correct, if you are trying to utilize it for a sole method of heat and cool. You will still need to dump excess / add additional through more conventional means, depending on local climate.

To your underlying point, none of the added complexity is worth the effort unless a) the utility is paying you to take the excess load and/or b) someone really innovates on a slick, simple package.
Firstly, your expectation that an axiom be true belies your misunderstanding of what an axiom is. Secondly, your expectation that something at all be true independently of personal experience shows your lack of acquaintance with phenomenology, or at least a refusal to understand it.
In my experience, the reason for this is deep specialization. Even for relatively simple jobs, it's very time consuming to get someone up to speed. For complex jobs it's sometimes downright impossible.

Bosses respond by heaping more work on the employees who already know what to do and can achieve it efficiently.

You should respond by asking for a raise. Be tactful, do it a few times and then use it as an argument. It really doesn't matter whether they pay you for overtime explicitly or as part of your base.
It's a political problem, not a technological problem. We have the ability to use waste to fuel fast-neutron reactors, which not only reduces the amount of waste but makes it less difficult to deal with. The problem is that one output of these reactors would be plutonium, and due to anti-proliferation treaties it opens up a political can of worms.
Because you’re comparing a workstation class out-of-order CPU design to a teeny tiny embedded chip lacking an FPU or even a unified code/data cache. It’s like saying “how does the Intel Atom compare against the AMD Ryzen Threadripper core?”
My rule of thumb is always "which version is easier to understand and verify for a code reviewer?"

Sometimes doing DRY means you've nicely separated out and encapsulated the common code that can be checked just once in isolation. Sometimes doing DRY means you end up with a complex abstraction that is hard to understand on its own.
Chisel looks nice. Thanks for doing it

I would be happy to use the site for publishing software. But to see if I can rely on the site for backup, aswell as simply general interest; I would enjoy reading (maybe a page on the site) about where it came from / what your plans are for it / longevity / intent

i.e. I want to hear more about you ;)
I want a social network consisting entirely of people who have walked the walk before writing about it please. The r/ask* subs are a decent start. Experts in their field who tweet about their field (and not unrelated bullshit that's hard to filter out) are also great. Would pay.
Itch is a 2 engineer operation. Its incredible.

They could undercut steam by 20% for each sale.
AI Economy: How Do You Make Money with Machine Learning?