skysight-inc/HackerNews huggingface dataset:
Alphabet Earnings Report Q3 2022 [pdf]
India orders Google to allow third-party payments, slaps another fine
That used to annoy me a lot, but then I installed https://addons.mozilla.org/en-US/firefox/addon/skip-mobile-w... and forgot about it.
Oh yeah, you're right, I mixed up the terms. I just started learning about this topic and I got excited and wrote the post. I'll fix it ASAP. Thank you very much for spotting it :)
Another iterator proposal from the Go team
Depends on where in the Bay Area you were:

https://earthquake.usgs.gov/earthquakes/eventpage/nc73799091...

Santa Clara had 2 seconds of advance warning, and Sunnyvale had 4 seconds. San Francisco got 18 seconds of warning, though was outside the "ground motion" zone.
May also be good to benchmark against attrs which also seems to be similar to what you want to do.
Right, we are witnessing a project switch to semantic versioning that did not have it before.

I don't know when semantic versioning was invented, but it only became prominent in the last decade. Graphviz is from the 90s.
Microsoft Earning Results Q3 2022
The Communist Party won't take the bait. It took the US decades of neocon foreign policy in the post-Soviet states to manufacture the Ukraine war. It will take much longer in Taiwan because there are no ultranationalists to use like Azov/S14/Svoboda/Right Sector in Ukraine.
Last night the AI and I teamed up to write bedtime stories on demand and on the fly for whatever themes my daughter mused. I think about a billion families would enjoy an app that did that.
There is some utility that. I haven't seen blogs offer anchors per paragraph but would serve the same objective.
I don't think good practices is enough. It's all the little bits of knowledge about what works and what's the right way to do things that you pick up over years of working in and around a framework. Could an excellent C++ dev become and excellent developer working in React with Redux and Typescript and NextJS and Material UI? Of course. And probably less effort than training someone who's never written code before. But that's way, way more than just learning some good practices. It could be _years_ of collective effort (or more likely, just slowly written not-so-good-code) to bring a team up to an advanced or expert level.

Hire for your stack is absolutely a good idea, unless you have no other option.
The question is how do you handle the empty case for the hundreds of fields you pull from other systems.
Philips had 412,000 employees in 1974. Huge in its heyday. Currently 78,000. Sadly mismanaged into irrelevance for decades.
The bug that's currently blocking me from any work using master is https://github.com/ziglang/zig/issues/12325

That's not really a bug related to unfinished features that might get replaced anyways, but simply one involving recursive structs with pointers between, i.e. linked lists.

Not detecting issues like these feels less like a "these parts are unfinished hence here be dragons" thing and more like a fundamental culture problem.

I'm fine with cutting myself every now and then with a sharp tool and cutting edge technology, but that can also be done while having a ever growing and mature core that promises at least some stability. The only alternative seems to be to pull a Hickey and work on it for two years without releasing anything.
Fair enough, one misconception I always hear from people learning about Godel's incompleteness theorem or the halting problem is that it means there exist algorithms where we can never know if it halts or not. Like there's some limit to math that makes it impossible for us to know whether a particular algorithm just keeps running forever or will eventually stop.

No such algorithm exists, no such example exists because for any particular algorithm it's always possible to determine whether it halts or not (at least in principle). It might not be practical, the proof might be incredibly difficult, but math does not have any kind of intrinsic limitation that prevents us from proving whether a specific algorithm halts.
I got an Apple Watch in the endgame of my PhD to catch all the thoughts I'd have out and about, particularly on runs. I rarely reviewed them and a lot was adrenaline-induced ranting and raving, but the act of documenting helped cement them better and drastically cut out the anxiety of potentially forgetting something really good.

David Lynch analogizes his sitting-with-cigarettes-and-a-notepad-to-catch-ideas to fishing. You can't chase after them but once in a while a big one will come along.
Eh, no, you are not allowed onto the ship. Still, it is probably the best museum in Sweden.
By my count its 23 years.

The biggest issue in FOSS is folk don't wanna join a "good enough" project and move it. Sometimes the project is contributor hostile (rare?)

And we end up with basically:
"I'll build my own moonbase with blackjack and hookers!"

All that starting from scratch costs loads of impossible-to- recover-time.
The "fantasy" part of this things is the price... For that price I can get a full computer/ chromebook that supports Linux, I wouldn't put more than 100 bucks on something like this when ALL it can do I can do it with Termux on an Android phone...
ShakeAlert and similar systems are awesome, but not exactly what most folks mean by a prediction, FWIW. They're meant for warnings of seconds, but not for things on the scale of minutes or hours or days.

Not to take away from ShakeAlert in any way though! Just clarifying that in terms of another comment I made about earthquake precursor signals.

ShakeAlert and similar aren't about precursors, but instead are about "the earthquake has happened, let's tell folks before the damaging surface waves reach them".
myshake pinged my apple watch while i was recording a cat. Cat definitely did not detect it before myshake, I don't think he even noticed it until the actual shaking.
An if statement without an else can have the case where line coverage does not cover the "don't take the branch" part of branch coverage. Therefore, if not taking that branch results in a bug line coverage only will not pick up that bug. -- For example, if you initialize a value in an if statement's then branch but don't have a default value for it or an else branch to provide a default.

Or even if you have a ternary operator (which has an implicit if-then-else take/don't take branch) that is usually only one line.
Also not discussed - the wayland version implements a lot more features, comments, and boilerplate. The one in OP is 178 lines with comments and features basic window control.
In XML world, XDM (XPath and XSLT data model) is the de facto standard on how to interpret whitespace.
A basic example looks like: https://github.com/davidfowl/CommunityStandUpMinimalAPI/blob...

Some more documentation on integration tests: https://learn.microsoft.com/en-us/aspnet/core/test/integrati...
Plugging here my "text-adventure" mode of Doom that runs on.. wait for it.. Twitter [0] :-)

[0] https://twitter.com/tweet2doom
Too much marketing speak I think.

> We're planning Turbopack as the successor to Webpack. In the future, we plan to give Turbopack all the tools needed to support your Webpack app.

> Currently, migrating to Turbopack from Webpack is not yet possible. In the future, we're planning to offer a smooth migration path for all Webpack users to join the Turbopack future.
This is so useful.
> Formal verification also becomes practically impossible at a certain level of complexity.

Then reduce complexity.
predicted a 4.8 about 5-8sec before i felt shaking in redwood city.
it could do what figma does, use web assembly and web workers
No, if you like it, go for it. Seems better than getting laid up for a week if that's the alternative. But you seemed surprised that anybody might decline to get one.
Blood type is weird but in Japanese cultural it's similar to adding your Myers-Briggs type.
I once spent 20 min trying to find which streaming service had the latest season of the Orville in New Zealand. Turns out none of them do. I tried to find a digital copy on every store I could think of and failed. I looked for the Blu-ray and learned that Fox isn't ever releasing one.

The whole time in the back of my mind I knew exactly where I could find it for free without any pain at all.

In my book if there's no legitimate way to get a digital copy then I'm sailing the high seas. The golden age of streaming is over.
Almost no languages run as WASM.

This is not likely to change anytime soon (if ever), as nobody is working on this, and there is even quite strong opposition to get features in that are fundamentally needed to run anything else than the very few languages that already compile to WASM. ("Nobody" is interested in invalidating their investment in JS ;-)).

Also WASM is actually slow, or better said, "it does not deliver its full potential".

It will need advanced JIT compilers to keep up with the other two mayor VM langues. But in this regard WASM is behind around 20 years of constant development and improvement.

My strongest hopes in this regard are currently with Microsoft (even I don't trust this company at all!), who are indeed interested to run their CLR stuff in a WASM VM, and could probably deliver on the needed features. But then, when you would run a CLR-VM (or a JVM) on top of a WASM VM, you know, you're building just the next Matryoshka… There are no real benefits to that besides "look mom, it runs in the browser".
It is not.

Other article from the author include (title only) "Why Biden Favors Foreign Over American Oil", "Why The Woke Create The Disasters They Warn Of" or "Biden Is Failing The World".

Substack claims this person as "thousands of paid subscribers". I am fascinated by that.
We don't need "rewrite everything in Rust", rather "rewrite everything in safe languages".
It's Shellenberger so you can safely assume most of the blog is ranting about how the woke leftist cultural marxism blah blah blah. Red meat posting for people with the same priors, nothing of substance worth analyzing for certain.
Webpack was flexible and “good enough.” But it turns out rust-based bundlers are 10-100x faster and so the definition of “good enough” has changed, for good reason.

It’s hard to overstate how game changing this new wave of zero-config, ultrafast rust bundlers are for the day-to-day dev experience.
What do you mean by "still"? I just learned that it exists a month ago! I wish I was joking...

JS is not my main language, true, but damn it's hard to keep up. I think it took me less time to be productive with Typescript than with webpack.
> just block [WebRTC] entirely

I think an opt-in permission seems like the way to go, like the one we already have for microphone/camera permissions, and possibly just merged with these (i.e. grant WebRTC permissions together with A/V permissions).

There are quite a few interesting non-A/V WebRTC applications around – these could be handled via an explicit prompt, similarly to how newer iOS versions handle local network permissions.
It is also the primary language taught to bootcamp developers looking to get started, and so a lot of suggestions and ideas come from people without any real experience.
At my last job. I was there for 5.5 years. I changed teams every year or two working in widely varying projects and roles. After leaving, I had a hard time getting my resume to be believable.

So I think once you’ve worked somewhere long enough, there’s a good chance much of what you know how to do doesn’t “fit” on a page anymore. So when you see a boring long stint, I wouldn’t trust it. This “I know you’re ‘lying’ to get a job” feeling always applies, but now instead of thinking the applicant did “less” it’s the other way around. You now have to wonder if you will offer enough for their experience and if they’ll get bored.
Java supports curly quotes?
No, you cannot compute BB(k) for a given k.
https://scottaaronson.blog/?p=2725
> 10 years ago we bought every Minitel in existence from eBay and connected them into a giant X.25 network spanning the globe. Unfortunately, one EPROM didn't have a cover over its window and bright sunlight in Madrid caused firmware corruption.

What a tease. If only.
I really have my doubts about a meaningful drop in home prices.

The issue now is that there's a drastic affordability gap between those who own a home and those who are looking to buy a home. Because the vast majority of mortgages have their rates locked in, if you own a home and decide to sell and get another home, you're going to get much, much less for your money, since you're trading into a much higher interest loans.

That creates a huge constraint on housing supply. Unless you have a very good and/or urgent reason to sell (death, divorce, relocation), you're almost certainly going to stay put. The usual reason for a home sale - moving to a larger or nicer property - is out the window unless you've had an enormous increase in income/wealth.

Thus, even if demand is high (which it's not, because renters face the same affordability issues if they choose to try and buy a home), the severe supply constraint is likely to keep a pretty significant floor on housing prices. The two big things that could affect this would be newly built houses coming through or Boomers starting to die in large numbers, thus forcing sales. Neither of those seems likely to materialize in large enough numbers at one time to drastically move the market, given the data we have on housing starts and death rates.
No? Take this code:

void foo(int arg) {
int *x = malloc(sizeof(int));
if (arg) {
free(x);
}
}

If your test only ever calls `foo` with a non-zero `arg`, you have covered 100% of the lines in the function, but you never discover the memory leak bug in the case where `if` body isn't executed.
As a performance nightmare you can't wake up from, SCSS can't die soon enough. As someone who depends on it currently though I def understand the frustration with losing support.
Which in turn got its name from old swedish “rám” or “ravn”, meaning “raven”.
First off kudos to Ivan - both because i love being a fan of the underdog, but also because what he built really is great! (Maybe a little also because i am definitely NOT a fan of adobe. sorry.)

There are a cople of quotes here that are intriguing to me...

> "...From 2012 - 2016, Photopea had no monetization plans built in. And after graduation, Ivan only produced $29k in the first year and a half of monetizing..."

"Only" $29k!?! "Only" $29k!? I don't know about anyone else, but i actually find that number to be wonderful. Not everyone needs to be facebook-level monetized for their first year. I wish my startup/saas service monetized that much on its first year!

> "...Photopea is web-based, but it also is completely built using Javascript with no backend. This means it works offline with no internet connection and doesn't require huge computing power..."

I'll admit that when i first learned of photopea - from my offspring no less during one of their homework assignments! - i was impressed right away. Even if it was online only...But i guess i never knew that it can be used offline too! I guess i'll have to play around with it offline. Further, if it is in fact offline usable, well that impresses me a bit from a javascript perspective. I'll admit that i'm not the biggest fan of javascript...but if this kind of comprehensive application can be built with javascript and be usable offline, that's pretty dan impressive, and i guess i gotta give javascript much more respect (and of course play wuith things myself). (Yes, yes, i know that there are Electron apps that leverage lots of javascript for offline purposes, etc...but this thing was built on mostly maintained by one person!)

Finally, I really appreciate that they noted that this was not one of those instant success stories.

> "...these features weren't built in a day, Ivan spent the better part of 10 years slowly building out Photopea! He's solved over 4,000 feature requests and issues on GitHub alone!...With no paid marketing, Photopea found success through AMAs and old-fashioned, word-of-mouth sharing..."

Once again, kudos to Ivan for such a wonderful thing that he built, and for providing with himself a livelihood!!
Thanks for confirming. So what does Zig actually do to execute async functions? Green threads in the background? An event loop? Is there documentation on the implementation?
it's not hype. You get to write off a whole class of problems. You get new problems instead, but they're better ones to deal with. That said: is the VP also an individual contributor? Why is this change happening? That part seems a little odd to me. But I have engineered my career to write elm on the frontend and not another language because there's a whole kind of problem that we don't have anymore.
The Halting Problem forbids you to build an algorithm that proves if a generic problem halts or not. This doesn't forbid you to check if a specific algorithm halts or not. For example, you know that the specific program `print("Hello World")` halts. So you can remove the ones that do not halt by inspecting them one by one and developing a specific algorithm for each one that determines if it halts or not.
// @TODO implement and publish
import { webpackConfigTranslator as translate } from ”turbopack-webpack-compat”;
import webpackConfig from ”./webpack.config.js”;

const turbopackConfig = translate(webpackConfig);

export default turbopackConfig;

Any takers?
This is definitely not true for every legislation.
See also: MLton and whole-program compilation.
Yeah but that is mostly the problem with C++, and I am a big C++ fanboy, too many people write C style code with C++ compilers, to the point that Bjarne keeps doing tireless keynotes about how to write idiomatic C++.

Just the other day I found a relatively recent C++ tutorial on YouTube using Turbo C++ for MS-DOS, imagine how idiomatic it looked like.
Well, of course; why would you want to keep the initial clipboard forever? This is exactly the same behavior as for ^C/^V. I don't understand the purpose of your question.
It has a $3/month Premium account tier for no ads, increased storage, and double the steps history.
With rules_nodejs you can transform your source with whatever node-based packages you’d like. But be prepared to be more or less entirely on your own to figure out how to make it all work.

Oh and if you create many smaller packages (as is best practice in bazel to get good cache efficiency and parallel builds) be prepared for nonexistent editor/IDE support.
I feel this could be applied to the production of EUV mirrors:

https://phys.org/news/2022-10-telescope-mirrors-sharpen-view...
As someone who has only built Node/TypeScript or .NET APIs for the past few years, I can say that the ecosystem of .NET is dramatically better than Node. Everything works and there's a high quality library for everything.

The only thing I miss is the phenomenal structural typing of TypeScript. That by itself is enough to tempt me to use Node sometimes.

So I guess I disagree with everything you said, in the end :)
I love that article but that does not state what you are claiming it does. What that states is that there exists a k (whose upper bound is 8000) whose solution is independent of ZFC. That does not mean it can't be computed.

In the very comment section of that blog post someone brings this issue up, and Scott himself says:

"Yes, fine, you’re right, there’s not a single “boundary between the knowable and the knowable.” What there is, is more like a concentric series of boundaries, with signs warning you that as you proceed outward you need to take on bolder and bolder axioms (which might be large-cardinal axioms and might be something else). What’s significant about going beyond ZFC is just that, by that point, you’ve clearly passed the first of those boundaries."
It offers paid account for $3.3/mo with 5GB of cloud storage. See red Account button on the menu bar.
Phrasing like “2023 tax year” typically means for taxes paid in 2023 (i.e. your return will be due in 2024 with any concomitant payment/refund). So this won’t take effect for another year, basically.
If you have some free hours in Stockholm, treat yourself a visit to the Vasa museum. Seeing these ships with your own eyes and internalizing the amount of work and thought that was put into them is a real thought provoking experience. The eventual magnificent failure of the ship only adds to the story. This is one of the more impressive museums I had the pleasure to visit.
It's an old form, implying more that the person is going to tell you about what they learned than that they will teach you things.
> We can always have a JS layer for configuration while the core runs in Rust, much like for many Python libraries, the interface is in Python while the computation happens in C++.

And this behind-the-scenes-native code-but-pretending-to-be-Python is the reason why most Python stuff I try fails to run on the first tries.

Half of them I give up because I don't get them running after going down the weirdest error rabbit holes.

No matter whether Debian, Ubuntu, Windows 7/10, Cygwin, WSL2, Raspberry Pi, x64, ARM ...
Arno's Engram Keyboard Layout
Engram v2.0 (“Engram”) is a key layout optimized for comfortable and efficient touch typing in English. Letters are optimally arranged according to ergonomics factors that promote reduction of lateral finger movements and more efficient typing of high-frequency letter pairs. The most common punctuation marks are logically grouped together in the middle columns.
https://wiki.gentoo.org/wiki/Wayland

Found that pretty quickly and it doesn't go down a point-by-point feature comparison but gives you some idea of what's up in the "introduction" where it notes that Wayland doesn't include things like keymapping functionality, so that's all up to each compositor to implement. Excerpt:

> From a user's point of view, Wayland is nothing more than a framework. In particular, Wayland itself does not implement any display server that should correspond to the Xorg server. In Wayland, compositors are display servers, implemented by various projects. A compositor also serves as X's window manager (and X's compositor).

> This means users first have to choose a compositor, and via that compositor they "configure the server", i.e. set screen resolutions, input and video drivers options, etc.

> [...]

> Some lack of specification results in chaos more or less. For example one common complaint as of 2021 is that key remapping is absent in the Wayland protocol - in Wayland there is nothing that corresponds to xmodmap of X. Each compositor offers, if any, their own way to remap keys.

> The situation however is not totally random - many compositors depend on the library "wlroots", which abstracts such common tasks, and is aimed to be impartial. First started as a subproject of the compositor Sway, it now is used by many compositors. Exceptions include mutter and KWin, i.e. GNOME and KDE, and Weston.

TL;DR minor WM/DE projects have circled around wlroots as a life-raft to fill in the missing functionality, while major ones have gone their own way, resulting in extremely basic functionality potentially being wildly different (and having a different set of bugs and quirks and how-to-configure-and-use-it) depending on which compositor you're running, or even simply being absent on some.

[EDIT]

Unsurprisingly, Gentoo's cousin distro (if you will), Arch, has an even better page on it:

https://wiki.archlinux.org/title/Wayland

Note especially the part where it's possible for a given compositor not to work with certain graphics hardware, while others will. That's how little help Wayland gives to desktop environments and window managers. To get the equivalent of Xorg you'd have to get everyone to agree on a single fairly-big and featureful compositor and only use that.

Or, good lord, look at the display manager support table. LOL.