skysight-inc/HackerNews huggingface dataset:
I benchmarked Laravel, Django and Symfony a year ago in a rather minimal setup on all three. From what I can remember, Laravel was a good amount faster than Django, and Symfony a bit faster than Laravel.

Take this and a basically every other benchmark with a huge grain of salt as the frameworks have quite different functionality enabled/installed out of the box.
English is not my native language. And these kind of debates demand a very careful choice of words that are often not easy for me to find.

That's why I'm rather reserved in these types of conversations, not because I doubt that my point is valid.
There are conceptions around color being an inherent property of an object, independent of the light coming from/to it. "The book is purple". Turning off the lights doesn't mean the book has changed color, and now is black. And it still is a purple book, even when under red light it looks red. Sort of "object's potential color if lit with white"?

If one thinks an object is the color it reflects, then add confusion about refraction, and one might easily get to "it looks blue but really isn't".

Science education echos stories, and sometimes those are less than wonderful. Like tabloid journalism narratives, missing the point and leaving readers confused and misled. As with "color from refraction, constructive and destructive interference". IIUC, that interference is mere description of wavelength-dependent differential bending - you still need to absorb the colors you don't wish emerging. But emphasizing "it's not pigment color, it's structural color!", rather than their similarity, can parse as reflection/absorption vs refraction, and conceptually interbreed with real vs apparent object color.

Stories like [1]. The "constructive interference" is "cancelling out" wavelengths, which "is why your eyes perceive" blue. Rather than say, here's one of several mechanisms for pigments to color objects.

[1] https://www.youtube.com/watch?v=29Ts7CsJDpg&t=113s
Harder Than It Looks, Not as Fun as It Seems
People act as if they are great communicators with their code. Most developers are terrible communicators in person/text so even worse using a language. Having comments plus readable code is nothing but a net-positive.
Yeah, and we already have TypeORM in Node, which is an excellent ORM (despite some clear haters here in the comments).

This is why Deno is a dead-end. We have tons of excellent solutions in the Node-verse, and they need to build everything up from scratch (or create ports that are "unstable and shouldn't be used in production" [1]).

And it's not just the ORM that's interesting. It's the tooling that will connect, say, TypeORM or Prisma.io to GraphQL, so that you can throw up an API in a few lines of code, that means you're writing something like 1/100 the number of lines of code for equivalent or even superior functionality.

[1] https://github.com/denolib/typeorm
Isn't it interesting that the "No Comments, EVER!" blog post allows comments!

(yes, I realize it's a different type of "comment")
What actually ever happened to Spotify's lyrics support?

They had something good going with musixmatch I think, then that went whyever, then that weird "behind the lyrics" feature came.

It's cool, but why not move that background info elsewhere and just keep the lyrics?
Yeah. I've often seen TDD where you act both as the logic programmer writing the tests and the imperative programmer writing the implementation.
[insert link to infamous HN Dropbox comment here]
True, although sometimes mawk is installed, as others mention.

If you need gawk, put gawk in your shebang, and if nothing else the end user has a chance at understanding why they’re seeing a crash. Also it will crash on line 1, nice and loud.
Debian & Ubuntu have moved back and forth between using mawk or gawk several times.

Debian Jessie (circa 2016) used gawk.

Debian Stretch (circa 2017) used mawk.

Today, Debian uses gawk.
Regardless of whether ORMs or SQL are more effectively database-agnostic, how often are you changing databases that this is even a concern?
Sign of extremely low effort article.
https://en.m.wikipedia.org/wiki/Compose_key
Having looked at a lot of the issues surrounding Tesla, I would strongly disagree with that statement. I think it's mostly informed by hindsight. While it remains speculative it is certainly possible that Tesla is in the same league as Wirecard, and maybe Enron.

People are easily thrown off by the fact that Tesla is successfully delivering a physical product and that the product is excellent in many aspects (driving UX, charger network, software integration, EV evangelism etc).

However once you look closer, a whole host of parallels emerge: 'Very aggressive accounting' (non-GAAP, 20% accounts receivables, junior CFO, warranty repairs as goodwill etc), business is not profitable (revenues stem from tax credits not cars), bail out/enrichment of Musk family (SolarCity), securities fraud (funding secured), retaliation against whistleblowers, silencing/threatening critics and journalists, legal record, occupational health violations (injured workers not being treated, Covid), workers at the factories not being allowed to speak to visitors, selling something that doesn't exist (FSD), environmental concerns at Fremont, ...

It's a different business than Wirecard for sure, and only time will tell, but the red flags are all there.
I'll be honest, your reply is kind of all over the place, so I don't know what you're trying to get at.

How are you expecting TikTok to "screw" its users? And what's the big deal with users just leaving the platform if this does happen? I really don't see the big issue here.
*Teething, for sure.
Wow, you hit the nail on the head! To point to our long term vision, cryptocurrency has the nice property of being data, but the double-edged feature of being money.

In order to tell people how to get data from point A to point B you suddenly have to be a fiduciary financial adviser! We want to take that duty seriously and help people interact with the cryptocurrency ecosystem as a trusted adviser.

If we can help you customize and interact with smart contracts and plug them into existing regulatory frameworks, then we can unlock a lot of value for everyone.
Almost all space reactor concepts have fresh fuel at takeoff and then start-up once they're launched. You can hold fresh nuclear fuel in your hand with very little hazard. It's only once you start splitting atoms that the radiation levels get high. So you launch the fresh and mostly inert reactor to avoid this risk.

RTGs, on the other hand, are radioactive from the get-go, but are usually quite small.

The USA did run a reactor in space (SNAP-10A) and the Soviets did a few dozen.
Let's say we work on the "reverse list" function. A few tests I could write are that the following clauses are true:

rev([1], [1])
rev([1, 2, 3], [3, 2, 1])

And maybe also that the following clauses are false:

rev([1, 2], [1, 2])
rev([], [1])
rev([1, 1], [1])

Is Prolog able to infer, from the above, that rev([4, 5], [5, 4]) ? Or to synthesize the general form rev([H|T],R) :- rev(T, RT), concat(RT,[H],R) ?
I was taught in business school (early 2000s) that it was good that GE fired the lowest 10% performing employees b/c the employees were not actually happy or content at GE or they would perform better. Therefore firing them is good b/c they'll find a better career fit elsewhere.

But I actually think it is terrible. It pits co-workers against each other and makes taking credit for an accomplishment more important than doing what's best for the organization.
1000 Amp Hot Knife [video]
It's a hyperbolization prop (frame from a classic movie where main character is as passionate about small things as an individual can get, to the point where it even looks ridiculous)
I worked on two projects that used ORMs; Java and Node and it was a total shitshow. The reasons are well known and too many so I won't get into them.

My sense is ORMs are terrific to get a quickly launch a product/project i.e., 0 -> 1 when worked upon by a small (3-5 member) team. But as a project succeeds and more people begin contributing it derails very fast and very badly. By the time an experienced data person comes in and sees the mess it'll be too late. Foreign keys everywhere, incomprahensible auto-generated queries, all sorts of joins etc., So they won't touch a data/model layer with a 100ft pole and continue to get entangled. When a data layer becomes unsalvagable the project is doomed. No amount of re-design/refactor/re-architecture can revive a project if the data layer is messed up.

Data model is the heart and soul of a software please don't outsource its design to an ORM. There is a good reason Linus said something to the effect of "Bad programmers worry about the code. Good programmers worry about data structures and their relationships".
Level 0 data science: "We have several datapoints."

Level 1 data science: "We have several data."

Level 100 data science: "A relation have a fixed number of attributes (columns) and each column have a domain [...]."
Mister Car Wash sets IPO terms that values the carwash chain at about $5B
Shameless plug: this is what we do in EdgeDB.
Pretty much, yeah. It's yet another sign that JS/Node should have had a keyword to let async functions appear, to the calling code to act async, rather than requiring a keyword to stop that. IOW its idiom is backwards from what would be best for the programmer in the typical project. The other signs have been... every live codebase using every previous method of dealing with JS & node's async patterns. "Callback hell", the very common pattern of using promises to wrangle async code into acting synchronous, and now "await", comically, prefacing more async calls than not.
Interesting. I've been in and out of the .NET world over the last 15 years, and I've used Visual Studio. If my employer sprang for MSDN, I'd use Professional, but for most projects, Community worked great. I did have access to ReSharper at one point, but I didn't end up using most of the features. I've found in my own workflow, you don't need any of those things, though I'm sure some people rely on them for some personal efficiencies.

At any rate, I've never found even the free Visual Studio Community to feel like a "basic editor."
I guess it depends on what you would label as political. Breitbart (sigh… I know) stated that “Politics is downstream of culture”. It’s not a new idea but I have no doubt that these non-political spaces will serve as cultural funnels into various ideological bubbles.
They did when Verdi was alive, and then you did: https://archive.fo/zrx64
Then you shouldn't have put wire hangers in the closet ...
That applies to presentations as well.
There should be pretty strict regulation for fission reactor development, simply because radioactive materials in runaway reactions can have totally uncontrollable, millennia-spanning consequences. Very few other technologies have this potential - even a regular chemical explosion poses little risk to future generations in a large radius. Certain materials (plutonium, for instance) can reach criticality very quickly and in tiny quantities, and plutonium is a byproduct of fission. (I’m not a nuclear physicist, so my understanding of the real potential here might be wrong, because I have no sense of the quantities that might be experienced).

This isn’t a defense of the current regulatory process. The time frames, in particular, sound pretty egregious (4 years to approve a prototype, and 2m pages of documentation feels like a lot, too, but again I don’t know how these things are designed). But I would be extremely uncomfortable with lax regulatory oversight, given that nuclear accidents have permanent, irreversible impacts on society and geography.

Now, small-scale reactors may be a different beast entirely. If the quantity of materials is pretty much guaranteed not to have potential to cause problems for anyone but the operators for a short period of time…. Then there certainly seems to be a case for a shorter regulatory cycle. But I would be shocked if scale isn’t already taken into account for the current regulatory burden.
This isn't WSJ news, this is a WSJ editorial, which is generally pretty useless.
By "The Editorial Board"?

Is that collective responsibility, or individual deniability?
Found during the rabbit trail this sent me down. Sounds like something most of you already knew about, but I didn't. So, sharing on the off chance it's also new for someone else.

https://mcfunley.com/from-the-annals-of-dubious-achievement
This comment is out of place. That being said, after reading through the reddit thread, the developer Kovarex is extremely based.
And thinkers are automata with no empathy or compassion. Stop denigrating people for processing reality differently than you.
I'm a long time dotnet guy, but I've been working with Swift/XCode recently.

There are definitely some things I like (completions in particular), but man do I miss the dotnet world.

I recently had an issue where I was using a third party closed source library in Swift. A particular function I was calling was sometimes bombing out, and because it wasn't marked as a throwable function, I couldn't put a do/catch around it. As a result, when it did, my app would just crash and there was nothing I could do about it.

I even asked on StackOverflow and was just told that this function can't be erroring out, even though it was lol

I've worked with other languages/frameworks as well over time and nothing is as nice to work with as dotnet.
For anyone who wants really good compression of data with a particular characteristic, a very useful approach is to first shrink or reformat the data based on that characteristic, then pass the result through a general purpose compressor.

For this case that might mean convert the data into deltas, then write those deltas in a byte-oriented variable length integer fashion. The general purpose compressor can then pick up most of what you have left on the table by not being super careful with the balancing of the chosen integer format, and it might find some other useful patterns in the data without you having to worry about those.

Theoretically a single compressor crafted purely for the exact characteristics of the data at hand would be able to do a better job. But in practice the skill and time required to beat the hybrid approach tends to be a showstopper.
My first computer programming language was assembly language. This has served me well since this removes a lot of the mystery surrounding higher level languages.
There are ways to get around YT's automatic strikes. There are numerous 'music reaction' channels where listeners play the music video in a small PIP window, and maybe shift the pitch a tad so it's not 100% identical to the original audio. This approach lets them play back the whole song + music video.

Some rights holders are especially aggressive, and proactively search for infringing material, so this method isn't foolproof; if they manually flag it, the audio will be stripped from the video. But for the cases where the rights holders are happy to use automatic strikes, the workaround still works.
a positive feedback loop. High pay attracts talents, which if utilized properly, will produce higher profits, which in turn, can afford higher pay.
It's doable. First, you use a Golomb coding for the deltas. Tuning the parameters just right, you can get it to fit inside your budget with a little room to spare.

Then, to get reasonably good time complexity, you use that extra space as a scratch buffer - read in a chunk of input, sort in place (heapsort is good for worst-case time complexity), and merge with the compressed stream. It's not simple to implement, but it does work.
I have never understood why RDBs have such general concepts of primary keys, where you can for example let date of birth be a primary key, when in every schema I have ever designed or seen, all rows get unique integer IDs anyway.
Sometimes given the technology or interface, its necessary to tell the next poor soul what is going on. Anyone who has wrote code to interface with an external system knows the story of odd interaction requirements that need to be document for the person who is maintaining the code at the point of use.

Also, sometimes given teams and other requirements, a bit of an unusual use of the programming language can be explained away by a bit of ASCII art. Giving a programmer a mental model of the upcoming code can help with on-boarding new people.
Unit tests do break once in a while. 80% will never break once written and should be thrown away, but that other 20% will unexpectedly break in the future alerting you to a problem that otherwise you wouldn't find until much latter in the release cycle. I don't know have any way to know which tests are in the 20% and which the 80% to throw away, which is why I keep them all.

Of course the 80%/20% figures are estimates. The longer your code is maintained the more likely it is some tests will break.
isn't this actually the defining feature of commercial American television? You don't see a lot of incisive political commentary on Dancing with the Stars or a season of Survivor either

basically cleansing entertainment of anything that could be considered incendiary and replacing it with people doing funny dances is something the American ad industry came up with a century ago.

Like it's not as if American popular entertainment looks like German ARTE or some Scandinavian drama where politics and culture is baked into everything
Ask HN: How is something like Super.so built?
I came across fruitionsite.com which is an open source implementation, but it seems a bit different. It appears that they're simply re-writing traffic and not actually hosting the site themselves.

Does anybody have any guesses as to how Super.so (or similar) is implemented?
An Analysis of the Purchasing Managers Index for Forex
Yes, I think it would be absurdly easy to notice, because nothing in most people's feeds is remotely political.

How exactly would you propagandize a stream of improv skits, or dance videos, or pet videos? Every user's feed is extremely specific and deviations, even small ones, are easy to notice.
How about using alternative web frameworks? e.g. Nancy, coupled with similar alternative ORM, etc...
Quantity of libraries is a poor metric. Like I said, the standard library in .NET covers a lot, and lets you make everything from CLIs to enterprise web apps. And when you do need 3rd-party code, there are plenty of commercial and OSS options to solve your problem.
Visual Studio Community or even VSCode with Omnisharp is a very solid choice. You can easily write C# code of any complexity without any extra bells and whistles of Rider because the language itself is that good.
That draft is referring to the operation of their own DNS servers, not messing with third-party DNS.
Shipyard constructed floating nuclear power stations are a truly excellent idea. You get economies of mass production and scale in the factory to reduce costs and speed up timelines, and you get extra safety from being in coolant, decoupled from earthquakes, and in deep enough water to not have tsunamis. You have more weather to worry about, and piracy, but in the balance shipyard nuclear is one of the most intriguing ways to really decarbonize the planet at scale quickly.

In the US, Offshore Power Systems tried this in the 1970s. They hired 1000 people, formed a joint venture with Newport News, bought and installed the world's largest gantry crane at their construction yard in Jacksonville, FL, and got a license to construct 8 gigawatt scale floating reactors from the Nuclear Regulatory Commission. Wild story [1].

[1] https://whatisnuclear.com/blog/2020-01-26-offshore-power-sys...
Thanks for catching that! It looks like our service-worker is breaking the page while it pre-caches the app. It should revert to a clean page once all the files are downloaded.

We're putting out a fix ASAP!
TikTok is currently only a small percentage of the revenue. ByteDance has quite a few apps in China. Douyin (Chinese version of TikTok) is a big one, but they also have a very popular news app in China. They also have a separate app for longer videos than TikTok. And many other.
Thank you for this reference, title of the article is merely an attempt to adapt/paraphrase a famous quote, it's not at all literal (absolutely no comments ever allowed)
I don’t think that people back then had the same narrative needs as we do.

One could just as well speculate that what they recorded were things important to them.

If wheat or papyrus or irrigation or agriculture were important to them, they might record those things.

But also might record great threats to survival like pests or floods or drought.

You’re take would discount people in far northern latitudes hunting whales because there are easier prey.
What briefcase is better than a Halliburton?
Thanks for the browser report! We'll be pushing a fix soon.
It’s possible, but typically you then pay a higher price on the other point I mentioned.

I used to work on a library that solved a certain type of mathematical problem, written mainly in C++. It was built separately for many target platforms in production: different operating systems, processor architectures, compilers. Each supported combination of these might require special provisions in the code due to compiler bugs, hardware limitations, etc. Then you’d have diagnostic code that was only included in the debug builds used during development. There are more than enough preprocessor shenanigans to go around in that kind of environment already, and another layer for test-related flags and checks isn’t going to break any records for most readable code.
It's not outrageous but it's not a trivial expensive, either.
I’d say that the logical conclusion is that KPI’s are the problem here.

Let the team measure themselves, bit give them a clear mandate and shared purpose.

When teams are incomparable, no such rivalry can make sense.
https://visualstudio.microsoft.com/vs/community/ is free and is pretty complete for a developer.
I trust them personally. Jon von Tetzchner, the founder of Opera, left Opera to start Vivaldi once he felt management wasn't doing things the right way.
nice, this looks impressive,
frontend could use some work tho
an interesting research in this area https://journals.plos.org/plosone/article?id=10.1371/journal...
The other problem here is that unit tests never break (since you've mocked everything that can break) and therefore aren't worth running; it might be more productive to write them for TDD and then just not commit them.

That's fine for code that never changes, or that has no logic in it. As soon as you want to change some code, you'll want a portion of the tests to require modification and a portion to stay passing.
His employment and family history is a fact and has been reported elsewhere also. Hopefully Financial Times is credible enough for you [1].

Would you mind sharing the link to the article about Xi Jinping’s “incestuous relationship” with his daughter? I couldn’t find it.

[1] “The claims are driven by the fact that Mark Simon, Mr Lai’s right-hand man, is the son of a veteran CIA officer and has worked for US naval intelligence.”

https://www.ft.com/content/f1cb693e-2f44-11e4-a79c-00144feab...
Link to Dapr: https://dapr.io/