skysight-inc/HackerNews huggingface dataset:
Unsure how either of my comments could be read as disagreeing with your point - both mention physics/micro-models being stronger than pure stats, but maybe in spite of your "The problem is" phrasing you only meant to amplify or only read quickly. That said, I can perhaps respond with something amplifying & clarifying of our shared skepticism of the pure statistics approach relative to something "more detailed" that might someday somehow help someone.

There are probably a half dozen micro-model effects even non-experts could rattle off that have "trended" over the decades from your shoes & surfaces to various aspects of population diet, young-in-life identification / more-optimized-maturation conditions and on & on. Statisticians call this a "non-stationary sampling process" meaning the independent & identically distributed (IID) assumption is at best a weak approximation and at worst totally misleading.

Ways to measure how much evidence there is that IID / other distributional assumptions are failing do exist { such as some of the ones here: https://github.com/c-blake/fitl/blob/main/fitl/gof.nim and referenced at the bottom of https://github.com/c-blake/bu/blob/main/doc/edplot.md (at the stage where one "plots / pools together multiple data points into some kind of "sample" with a "distribution") }. Sadly, few test such assumptions (which are rarely truly comprehensive anyway) and even small departures from modeling assumptions may lead to relatively large errors in estimates. E.g., the linked to Einmahl 2009/2010 research states this as an assumption to apply the ideas, but then shows no test of that assumption on the used data.
Scala, OCaml, and Haskell all have very powerful type systems. OCaml and Haskell even have good ones.
From my mother, a very emphatic "Don't sleep with women unless you love them!"
thanks for posting! :)
Not at three key strokes, it isn't!
Because it works on its own, I consider the Short Stack the more impressive project.

Both are super exciting though. Maybe a few years down the line, we get some 2" LCDs integrated or something for truly portable play.
My theory is that JavaScript programmers who were forced into thinking this way for decades with their single-threaded runtime have infected other languages with the idea that this style of coding is not only good but furthermore that it needs to be explicit.

Thank goodness we have wiser language developers out there who have resisted this impulse.
I'd have expected the opposite, myself.

Unplanned pregnancies might happen to people who aren't ready to have a child, physically and mentally - or who don't have easy access to medical care.

IVF, in contrast, only produces planned pregnancies, and only in people with easy access to medical care.
The land requirement for cows you refer to is probably the US-centric one. That's not universal. For example, Australian cattle pretty much roams arid land not suitable for crop production. The food is supplemented but still the carbon footprint of Australian cattle is very different to US cattle.

My main point is that if we ignore the tragedy of the commons of land use (which we do), the energy cost of growing a cow is largely free.

Lab grown meat requires probably a sterile environment and you'll be paying for that energy. Where is that energy coming from? What is the footprint of that? Now maybe that density of lab meat production is really high but I'd be surprised. Large herbivores can gain hundresd of pounds a year just grazing.

I do believe in the future of industrial farming. I just don't think it'll be meat. It's more likely automated greenhouses of likely hydroponics. It's entirely feasible that this way can easily support a trillion people on EArth [1].

[1]: https://www.youtube.com/watch?v=OzVxdmC8c-g
OpenVDB Format: A Deep Dive
I think FAANG-like big IC offers right now are flying around for technical people familiar with the current hot "AI" methods. A lot of hype, a lot of situational ethics around copyright, and some investment scams, but some of the tech is ready for legitimate things people want to do, at acceptable quality levels for the application.

Also, one thing that happened early in the dotcom gold rush is that a ton of people swarmed in, all suddenly acting like experts and professionals, with little/no prior experience. Meanwhile, Internet people who were also prolific programmers were, like, who are all these people, and why do many of them have fashionable eyeglasses like nerds would never try to pull off. I don't know how much we'll see something like that this time.
Trunk: Build, bundle and ship your Rust WASM application to the web
> I wonder whether that impacts the longevity of these constructions.

Probably positively--Shikoku Island is quite a bit more tropical/humid than LA. I'd imagine a timber-framed house that has already endured centuries in a more humid climate would do just fine in a milder/drier climate.
How much of a consensus is there though, when as soon as you start digging at the edges, the consensus dissolves? And the edges are boundaries of the pool of the experiences we know. What about the experiences we don't know? What if we start considering not only agents with a physical body, but also add a dimension of agents without one (considering that the ways we recognize intelligence in animals is by the way they move)? Then our entire discussion jumps to the border, and the consensus is nowhere to be found, making the heuristic - again - biased towards the familiar.

No, I think we need a better heuristic than consensus. The consequences of a bad heuristics are, at best, wasting time, but at worst, pulling the trigger on something heinous because it was insufficiently understood.
> fully colorless for async means you don't know when things are async or not

The IDE can tell you.
Launching VHS: The Visual Haystacks Benchmark
Why wouldn't defcon allow this to be presented?
I would have thought that 1 in 4 EVs sold in Europe being Chinese imports and LGs strategic partner Tesla using Chinese LFP batteries from CATL for their mass market models would have more impact than the allegedly "waning" demand.
Haskell’s type system isn’t sound either, there is unsafePerformIO.

Nobody actually wants a language with a sound type system, unless they’re writing mathematical proofs. Any time you need to do anything with the external environment, such as call a function written in another language, you need an escape hatch. That’s why every language that aspires to real world use has an unsound type system, and the more practical it aspires to be, the more unsound the type system is.

Soundness is only a goal if the consequences of a type error are bad enough: your proof will be wrong, or an airplane falls out of the sky, or every computer in the world boots to a blue screen.

For everybody else the goal should be to balance error rate with developer productivity. Sacrificing double digits of productivity for single digits of error rate is usually not worth it, since the extra errors that a very sound type system will catch will be dominated by the base rate of logic errors that it can’t catch.
And then businesses start competition for the customer with pricing pulling that inflation down. No one will start new business or start adjusting existing in context of stimulus money to make prices competitive because they know this spike is just a temporal glitch. Business was rather interested in raising prices to get more in the face of supply shortage. Showed good corporate profit numbers.

Stimulus checks are nowhere close to ubi from person's and business perspective, I would not extrapolate observations from one to another.
> Async code bubbles all the way to the top. If you want to use await, then you have to mark your function as async. Then if someone else calling your function wants to use await, they also have to mark themselves as async, on and on until the root of the call chain. If at any point you don’t then you have to use the async result (in JavaScript’s case a Promise<T>).

I find many descriptions of async code to be confusing, and this kind of description is exactly why.

This description is backwards. You don't choose to use await and then decorate functions with async. Or maybe you do and that's why so many async codebases are a mess.

You don't want to block while a long running operation completes, so you decorate the function that performs that operation with async and return a Promise.

But Promises have exactly the same value as promises in the real world: none until they are fulfilled. You can't do further operations on a promise, you can only wait for it to be done, you have to wait for the promise to be fulfilled to get the result that you actually want to operate on.

The folly of relying on a promise is embodied in the character Whimpy from Popeye: "I'll gladly pay you Tuesday for a hamburger today".

Once you have a promise, you have to await on it, turning the async operation into a synchronous operation.

This example seems crazy to me:

async function readFile(): Promise<string> {
return await read();
}

This wraps what should be an async operation that returns a promise (read) in an expression that blocks (await read()) inside a function that returns a promise so you didn't need to block on it!. This is a useless wrapper. This kind of construct is probably the significant contribution to the mess: just peppering code with async and await and wrapper functions.

await is the point where an async operation is blocked on to get back into a synchronous flow. Creating promises means you ultimately need to block in a synchronous function to give the single threaded runtime a chance to make progress on all the promises. Done properly, this happens by the event loop. But setting that up requires the actual operation of all your code to be async and thus callback hell and the verbose syntactic salt to even express that in code.

That all being said, this piece is spot on. Threads (in general, but in ruby as the topic of this piece) and go's goroutines encapsulate all this by abstracting over the state management of different threads of execution via stacks. Remove the stacks and async programming requires you to manage that state yourself. Async programming removes a very useful abstraction.

Independent threads of execution, if they are operating system managed threads, operating system managed processes (a special case of OS managed threads), green threads, or go routines, are a scheduler abstraction. Async programming forces you to manage that scheduling. Which may be required if you don't also have an abstraction available for preemption, but async leaks the single threaded implementation into your code, and the syntactic salt necessary to express it.
As they should be.

I object to doing what a computer can do for me (in programming), and manually creating separate versions of functions that are identical up to async absolutely falls into that category.
But will you make FAANG salaries as an external? At my work these are the worst paid employees.
I'd recommend Metabase, we've used it for years with no issue. Very simple to use and business users can easily get the hang of it and build and filter their own reports.

While I'm at it, here's a killer Metabase feature that I haven't seen in other reporting tools I've used:

While you can save a report to folders and have pretty URLs (your.domain.com/sales-report), whenever you build a report or change an existing report, it gets its own unique URL. (It's long and ugly, but I don't mind.)

Here's how I use it and why it's cool:

- If you're building a report and make a mistake or want to try something else, the back button actually works!

- If you have an existing report (your.domain.com/sales-report) and just need to filter it quickly to (like show all sales above $10K closed by Sam this year) and send it to someone else for some quick troubleshooting, you just filter the base report and grab the unique URL and send it around! No need to save it to a folder.

- I have a library of SQL queries for specific things and I can quickly pop that into Metabase (rather than using the report builder) and send the URL to someone. Again, just not having to go through the motions of saving and naming everything that may only be short-lived is nice.

- Just generally love not having to save every little iteration or filtered version of a report as I often just need it for some quick troubleshooting or discussion. No need to have a junk folder of reports with stuff like ("Sam deals over $10K 2024").

Hopefully I'm explaining this clearly!
Amphetamines generally are way stronger than coffee and can really keep you up/kill your sleep. Not that this is just from my own experience, I have ADHD and a prescription. Sleep is perhaps the biggest issue I am still dealing with.
Was it only the last sentence that was wrong?

Would you mind indicating what advice you think the PhD person should have written to you based on what they knew of you at the time?

Genuinely curious, and thank you for the anecdote.
US spot Ether ETFs make market debut in another win for crypto industry
> I know it puts off some people who mistake that for anonymity and think this is ruining the web, that people can't behave if they aren't talking under their own name

I haven't run across this sentiment with regard to personal websites or blogs. Who is saying that?

I do see it for forums, comment sections, and social media. Those often bring together people who did not consciously seek to interact with each other, and do tend to reward antisocial behavior with attention.
I was referring to the difficulty overriding the various techniques certain modern software like this use to trigger automatic updates at times outside admin control.

Disabling a scheduled task is easy, but unfortunately vendors are piling on additional less obvious hooks. Eg. Dropbox recreates its scheduled task every time you (run? update?) it, and I've seen others that utilize the various autostart registry locations (there are lots of them) and non-obvious executables to perform similar "repair" operations. You wind up in "Deny Access" whackamole and even that isn't always effective. Uninstalling isn't an option if there's a business need for the software.

The fundamental issue is their developers / product managers have decided they know better than you. For the many users out there who are clueless to IT this may be accurate, but it's frustrating to me and probably others who upvoted the original comment.
This is exciting to see - it seems the last release of was a year ago.

Can anyone clarify if this project is active?
Server rez on a low level wiz build? That's way high level thoughts and prayers to the Top 500 (also a cleric build) or lim. "request" to the Blackrock genie over in Budapest. Besides, 7th? Pff, call "company of choice" to fight for you, save or die server vileness!, and of course "peon:cleanse everything? peon:what do mean everything? cleric:EVERYTHING."

Frankly you probably want a PRC, and at those admin levels much, much save or die. Probably got so many server pokes per minute you're gonna be furiously holy wording your file system all day long. Team members? Rez? Please. You solo that.

Low level wiz? "Welcome to name brand, and lack of female desirability, here's your special hat..." "Why aren't the lights on?" [1] "Help, I lit my own hands on fire!" [2] "Ah, every threat one hits me!" [3] "Man they target me bad at conferences, how'd I draw DARPA as agro..." [4] "Holy s*t there's a lot of documentation to write!" [5]

High level wiz? "Computation hates all magical ideas and their very implication!" "Curse your sudden but inevitable betrayal of my trust, our own company is secretly controlled by Orcus and seeks the death and slavery of all life on Earth" [6] "Join me in the bag within bag abyss together and we shall quest to Jubilex for glory and honor across the eternal battlefields of tomorrow!" [7] ITGETSOEPIC::THEYWONTLETULEAVE::ALREADYATWARP::AUTOLADDEREJECTED::HOWDIDRAWULTRONASAGRO::MIDASTOUCHISHORRIFYING::AHHHHHHH [8]

[1] https://www.d20srd.org/srd/spells/light.htm

[2] https://www.d20srd.org/srd/spells/burningHands.htm

[3] https://tvtropes.org/pmwiki/pmwiki.php/Main/SquishyWizard

[4] https://tvtropes.org/pmwiki/pmwiki.php/Main/ShootTheMageFirs...

[5] https://www.d20srd.org/srd/feats.htm#scribeScroll

[6] https://tvtropes.org/pmwiki/pmwiki.php/Main/FaceHeelTurn

[7] https://learn.microsoft.com/en-us/windows/uwp/cpp-and-winrt-...

[8] https://www.qwantz.com/index.php?comic=1355
Unfortunately you're quite right. Maybe because those workers are also "trained" to see what they do as unskilled work, like everyone else says? So unskilled work is what they deliver. Now if only the society would give proper attention and value to those jobs... Edit: I'm also a diplomed electrician, but I have never practiced and would not even dream to practice nowadays without proper updated training. I guess not everybody is that self conscious, because hey it's unskilled right, so here we are.
Becoming a cooler, fitter, more interesting version of yourself
Don't go looking for ideas. Either build for yourself or build for the obvious market gap in your industry. Anything else has a high failure rate.
My first thought was this is trying to be htmx as well, but upon reading the readme this project appears to convert the html it has retrieved from the API into a DOM object using the hmpl.compile() function. Could I do that with htmx?
I think https://gwern.net/ is a pretty good example of a "personal site" that in another universe could be a regular blog. https://gwern.net/changelog is the only log part of it.
Yup. I submit that this sort of threat poisons the well and makes security worse for everyone, including those making the threat (but it's a bit of a commons problem because the worsening security is industry-wide, but for the threat-maker it seems to improve their situation).

If I am a person interested in how these systems work, and maybe making some money off my work in the area, this sort of threat, both its severity (potentially years of costly litigation and or/jail) and how frequently it happens (seems we read of such incidents many times per year, which is only the tip of the iceberg) would make someone seriously question the straight white-hat path. Why not find the exploits and sell them on the dark web? One might even justify it with "they wouldn't listen anyway and it's their fault for releasing a system with such stupid vulns." and/or "they'll fix it only when they see real-world consequences and if they don't it doesn't matter". One's moral compass need not be very compromised to lean on such excuses.

There REALLY needs to be a Safe Harbor law with basic requirements that the work is documented, first revealed to the company security dept (perhaps citing the Safe Harbor law?), no action taken by the researcher to allow it to be disclosed or released publicly for 90 days, and perhaps a few other reasonable safeguards.

and how often it happens
How do you deal with it? Just by taking a break from everything I would imagine.

But what if that's not possible? What if you're in the middle of getting a degree or need to financially support your family and can't take a break from work. Any insight into what "dealing with it" means for you?
Right, but Google is surely the one at fault here. There should be absolutely no reason that this extension can "change all my data on all websites", whatever the hell that actually means.
The other downside is that it is harder to break into because there are less roles.
What do you gain from an unsound type system? Implicit casts still exist and one dependency returning Any means that your specification is meaningless (you can prove anything, including false).
overemployment in multiple 100k-150k year full remote jobs as a sr engineer

2 is easy to do, 3 is manageable. I've heard of people doing more than 3, but most I've personally seen someone do is 3.
I do side projects mostly for fun and not for profit though I had a site that made $1000+ in advertising revenue years ago. I've found there is nothing that gets recruiters calling than having a few good side projects on the web.

Although I've served on a standards committee (it is actually very easy to join one), for a while I've done most of my projects on my own for my own entertainment (such the "three sided card" decoration system that I use to make things like https://mastodon.social/@UP8/110607498804590869 and a long term project to develop a "second brain" that's been in various incarnations a job application tracking system, an RSS reader, an image sorter) but in the last few months I've made friends with someone who is developing a pitch for something to transform the world of online comments and I just met a seamstress whose friend owns a clothing store and she and I are collaborating on some garments with fabric prints based on my photography and computer graphics.
35 is 15% larger than 30. Our measurements for unemployment are precise enough that it’s not just margin of error.

At the moment, that’s a change of 16 million people. A century ago, it was 5 million people. Both of those numbers are large enough that they absolutely would get attention and public discussion.
Come on, Bastion is nice but nowhere as sophisticated as Hades. Neither the gameplay nor the replayability would have let you think the team had the ability at the time.

As for transistor, the story is basically "futuristic world is being destroyed by virus-type-invaders and your sword/companion is the key to beating it", with a predictable end and almost zero character dev.

Being able to make ok games doesn't translate to the skill to make a masterpiece.

It was a quantum leap.

It would be like saying you can deduce Divinity Original sin 2 would be amazing because you played the first one.
With the most likely outcome being 0.
What's the Mars lander issue?
The unforeseen toll of a digital childhood
That’s the GP’s point. It is strange that std::monostate was chosen as the name, given that the different Monostate pattern [0] was fairly well established in C++ circles.

[0] https://wiki.c2.com/?MonostatePattern

(originally discussed in http://ftp.math.utah.edu/pub/tex/bib/cppreport.html#White:19...)
Software engineers are not (and should not be) technicians
The next big tech trend will start out looking like a toy
Sounds like you don’t have a network of friends/family to provide recommendations.
Xterm.js – open-source terminal for the web
It was also introduced as a temporary spam measure.
> If Alice tells Bob something there's nothing preventing Bob from telling Carol.

This is only true in the absence of an agreement between Alice and Bob that Bob won't tattle.
Coal deposition peak not caused by delay in fungal evolution (2015)
AI Missteps Could Unravel Global Peace and Security
I think there is a misunderstanding on your side. You seem to mix up the soundness of the type-system with the property of referential transparency. Those are two orthogonal things.
Are they the original employees who started decades ago? If so, that’s no surprise. My aunt was in the same position years ago, despite my attempts to update her on modern salaries.

Those awesome salaries tend to be paid to mercenaries and not the lifers.
If you read a bit about it, you'll understand that Apple did not copy the Alto—they did something that was actually way harder. They created a better version of what the Alto was attempting to do, and got it to run on lower-grade hardware they could sell for 1/10th the cost.

But yes, Xerox knew exactly what they were doing when they invited Steve and his team in.
Sadly didn't have to turn out this way if people had used Chris's work.