skysight-inc/HackerNews huggingface dataset:
I've seen catastrophic moisture damage in every form of home construction utilized in North America from the 1850s to present day. Anecdotally the most common failure modes break down roughly thus:

1850s-1960s: Termite damage followed by rot. This time frame is notable for ready availability of dense, tightly grained building materials. Lumber from this time period shrugs off all but the most egregious wetting cycles. So what happens is high humidity attracts termites which break down the structure. This in turn gives rot a plate to establish a foothold and spread (slowly).

1970s-1990s:
This period is notable for a steady decline in quality of building materials and introduction of first and second generation engineered products. First-to-market siding products, condensation issues due to the aluminum craze in the 80s, and material adhesives edging out toward the end of their life expectancy all contribute to problems with mold/rot. Looser grained building materials also mean that when a problem is present it will quickly spread to larger areas of the structure than older materials would permit under similar conditions.

2000-2010: Easily the absolute nadir of home building in the US. The industry saw a massive influx of "budget" engineered materials, with no substantive changes to code to address the deficiencies of these materials. My personal favorite from this era include OSB siding that turned into a kitchen sponge whenever the paint layer was breached.

2010-present: same as it ever was. The market is still flooded with engineered materials that have a fraction of the life expectancy of more traditional materials. Building codes have largely caught up with the obvious limitations of these materials, however now the biggest issue is as a nation we are short two full generations of trained craftspeople in the construction industry and as such installation errors are rampant. This leads to more and bigger issues, bigger abatement projects, and in significantly newer homes. Case in point: a pinhole leak in a caulk seam on a window surround that resulted in all of the structural members surrounding that window, the wall cladding, the sill beam, a section of the floor, and several joists rotting out in short order. Root cause: didn't use plywood. Engineered sheathing acted like an enormous sponge both retaining and broadcasting moisture to all of the surrounding materials.

So yeah, you're not wrong inasmuch as according to theory and per code it is within the realm of possibility to use these construction methods and materials successfully. In practice, however, the least competent subcontractor on any given jobsite presents a hard ceiling to what one can get away with. You design a fault-intolerant system that has any flavor of complexity to it's installation and odds are good someone's going to screw something up. The Achilles Heel of modern vapor tight building systems is the fact that houses leak. Either through incompetence during the initial build or breakdown of materials over time all houses leak. Whereas older construction methods would tolerate this to varying degrees, newer systems do not.
It's usually not the disk space that's the bottleneck, but rather, the CPU instruction cache. On modern Intel and AMD CPUs, the jump from L1 -> L2 alone can triple the latency of a memory fetch. For a "hello world" application, that doesn't really mater, but for, say, an OS kernel, it becomes really important to keep as much of your hot-path code in i-cache as possible.
It doesn’t really matter because most of those psych grads aren’t and would never be capable of administering mental healthcare beyond what any of us can already find on Google.
Yes, they curate, but also summarize the the major pieces in their daily email. The summaries are not inflammatory or emotional. Think Walter Cronkite.
Same happens to me. Couple months ago it pointed me through some small villages instead of using highway, making me save ~3 minutes, for the cost of a lot of stress and less safety.

I'm now trying to find some better navigation system because im pretty sure at some point it won't be optional.
I can't speak for others, but I care about binary size as a user because it tends to be a reliable signal of overall software quality (though there are definitely exceptions).

I also find it incredibly frustrating when an application I rarely use fails to launch because it wants to force me to download, process and install massive updates for features that I don't even want.

As an engineer, I care about binary size because gigantic binaries tend to require far more time to compile, move around and work with. Gigantic binaries tend to be a reliable signal of slow, toxic, internal processes that chew up positive energy and produce cynicism and frustration in it's place.

It's not about the disk space per se, it's about treating waste as if it's a virtue.
> I do understand the reasoning (they don't want people committing poor quality code), but this implementation just seems completely backwards to me. It breaks the natural order. It's like saying we won't let you ctrl+s until your tests pass to make sure you don't commit broken code. Stop nannying me and let me get my work done!

Could it be that this problem is due to Zig's stance on "no warnings"? It's admirable to try and partition things into strict "correct" and "incorrect" categories. But with only static information it seems like there's always things that seem a little grey.
readability is important. specifically, operator overloading is great because it makes code look more like math. when translating from math to code, this is highly useful.
I appreciate that critique. So what would it take to make this pathway smoother?

Do you think interfaces might be a silver bullet? If so, what’s holding back the language from prioritizing this in the medium term? (For v2.0, say)

Or maybe the most useful improvements are anticipated to come from somewhere else?
What'd be high on your list?
To be fair to yourself, LispSyntax.jl is more of a proof of concept than something that anyone would want to actually do significant coding in as can be seen by the TODO list in the README[1]. It also hasn't seen any active development in several years.

[1] https://github.com/swadey/LispSyntax.jl
What made Albania the country they ended up in? It is quite interesting, in Sweden, a well known but controversial politician, (Hanif Bali), grew up in a camp in Iraq to parents from this group, and while he was sent to Sweden as a child, his parents eventually ended up in Albania. When I heard that story, I did not pay particular interest to "why Albania", but now I start to wonder why.
Mandatory- fossil fuels have been dead for millions of years.
It probably played a good part into the decision.
Works on my mobiles:

- iPad: two finger click, open in background (or long press, open in background)

- iPhone: long press, open in new tab

Both are reasonably crisp, though on iPhone I need to rotate to landscape unless I use a magnifying glass. :-)
Physics has the same strategy: Important and timely results appear in the four-page (now four-page-ish) PRL and the long-term paper wrapping it up appears in PRD (or PRA, PRB, PRC, or PRE).

Only drawback is that people primarily read PRL, so people try to squash long-form results into PRL alone.
Jane Street likely has the highest applicant to available role ratio of any company in the world. I'm sure some heavy filtering is required, and probably useful.
You know patents have a limited life, right?

x86_64 with SSE2 is also patent-free right now, as an example.
> I prefer when the function call is explicit, it is a bit more cumbersome to write, but there is less hidden complexity.

you hide and obfuscate basic operations with functions, that's worse, specially when you have to chain arithmetic operations, with functions it becomes ugly and unreadable
IME, general purpose "small" languages rarely stay small.

Even C has accreted a lot of features.

I think Python was small at some point.

Pascal was small at some point, but by Delphi had become quite big.

Go has just added generics.

I think looking at a "smallness" for a relatively young language is likely to be misleading.
Can Agile Teams Have a Design-First Approach to APIs?
You could use it to build python extensions.

https://pypi.org/project/setuptools-zig/
Is the first part similar to the "W function" from Tutte's A ring in graph theory (1947)? If I remember correctly, it generalizes the chromatic/flow/Tutte polynomial to yield a linear combination of disjoint unions of bouquets (i.e., a linear combination of ordered lists of natural numbers, describing the dimensions of the cycle spaces of each connected component in the state sum expansion of the chromatic/flow/Tutte polynomial).
Here's a whole thread on it: https://twitter.com/paulnivin/status/1377079987950395393

Here's an article on it: https://twitter.com/twcnewsletter/status/1453376624666112003

Echos and anecdata:

https://twitter.com/NovalisDMT/status/1172573166956437505

https://twitter.com/_sagesharp_/status/1173637138413318144
> Why does adding a socket into a wall cost more than $50? Should be able to just open the wall panel, plug in an extra cable, close panel, done.

what are you envisioning? using cheap consumer power cables inside of walls, and paying extra to have unused sockets hidden away inside of walls for years/decades, just so that it's fast to add an outlet?

we use screw terminals inside of the wall because they're cheaper and more reliable than the socketed connections. and we use heavy gauge cable with thick jackets for safety.
> Its democratic governments were overthrown in 60s and 70s (they sought independence, not following US orders), replaced with Shah

Iran has never been a democracy in its entire history. The supposedly democratic leadership that was overthrown was appointed, not elected. Mohammad Mosaddegh was not elected by democratic vote of the people of Iran, he was installed by feudal lords (Majlis) and a king (the Shah).

Today Iran is a theocracy, not a democracy. 70 years ago Iran was a feudal kingdom, not a democracy.

The Parliament of Iran circa the early 1950s could hardly have been any less democratic.
I thought Japanese government services were famously difficult for foreigners to navigate? Is this assumption wrong or is it just very effective for Japanese Citizens only?
Oh yeah, the stackoverflow sidebars are as much as an extreme sport as opening random pages on Wikipedia and following the references.
Well, maybe. Thing is, political/economical systems are kind of path dependent. It's easier to go from democratic to authoritarian than the other way around, for reasons that I should hope are obvious[1] The reality is that 70 years while a lot for a single creature, is not very long in historical terms. Things from very long ago can have a continuous effect that is hard to stamp out as groups and cultures form in society that benefit from the existing or new structures.

It's just not realistic to treat countries, organizations, or other large groups of people the same as if they are individuals, any more than it makes sense to treat a computer program like a transistor.

Of course, in the USA at least, there is a pervasive culture of pretending the past doesn't matter, but this is childish. Two books I can recommend if you want to expand your ability to think this way are Why Nations Fail and Prisoners Of Geography.

[1] But since common sense isn't so common: a democracy can vote to become authoritarian, but an authoritarian place can only usually become democratic by force. Also, a democracy, to survive, needs an economy that is dominated by a relatively large, not relatively small number of interests, so they will check and balance each other and no single interest can capture the whole system. But once you become authoritarian it is easy for the economy to decline, simplify and become less diverse (and thus even better fit for authoritarians). It becomes an attractor. Have you not noticed that authoritarian states have a tendency to suppress development/innovation sometimes when it seems "irrational" to pass up economic gains? This is to avoid creating more powerful elites that would compete with the existing elites. Once you own a huge enough part of the pie, it becomes more important to keep yourself on top than to make the pie bigger.
They've always floundered around trying to find something that stuck that could also have a path to profit.

Being around the edges of the tech orgs that went in early on Scala it often felt like the Scala ecosystem initially thrived (the likes of Twitter releasing genuine quality oss in particular) despite the lack-lustre job of Typsesafe / Lightbend to cement themselves at the center.

With play being given to the community, lagom being underwhelming and a bit of a catch-the-wave thing, it's only really Akka that endures on top of the core language, which isn't really a great showing after so long.
Here's a sweet example of proper use of operator overloading:

https://dlang.org/phobos/std_checkedint.html

where operator overloading is used to create variations on integer types, like specifying the behavior when overflow happens.

Besides, `a + b / (c * d)` is far more readable than `add(a, div(b, mul(c, d)));
> He’s a genocide denier (Bosnia & Cambodia)and blames the US (via NATO expansion) for the invasion of Ukraine

These claims have been debunked so many times, please stop repeating them.
> If you need the government to behave against the best interest of the people in order for your industry to exist maybe your industry shouldn't exist.

There was a "check cashing" store next to our DMV that solely existed to service people who visited the DMV. Our own government was unable to accept US tender.

This exists all over the place. The amount of servicing and companies that exist basically because of the government is insane.
Part of it is simply that the places we live, work, and travel are aesthetically bereft.
Someone will still have to pay the price after the niche is found.

If the technical debt is big enough it can cripple the growth of the company to the point a competitor that initially was behind -> gets ahead.

I can give one example in map making industry - TomTom vs Here in EU.
All of it is true, but the loneliness problem is at least partially caused by the poster personality.

We do use "Hi, Bye, Thank You, etc." daily but I'd say that we find participation in hollow US-centric keep-smiling or in overboard politeness distasteful. But we aren't rude on national level, only keeping quiet if there is nothing to say. Blabbing to keep someone comfortable is not a virtue we are known for. On the other hand is comfortable silence in sauna between my friend and me, but you don't get there overnight.

Winter is as bad as described, we even have a movie "November" based on novel "Rehepapp ehk November". The plot is of no importance, but you should know that the opening chapter sets stage and mood by describing poor villagers in rain, slogging in mud up to their ankles. In November, no less. It is a blessing when snow comes and really sets in December, as the mud is over and darkness slightly relieved. It gets much colder that -10C occasionally, sometimes for weeks on end.

I think poster hit the nail in the head with "Estonians, and the rest". At least most of the older people take this approach. There is of course the question who is Estonian or considered Estonian by natives. You won't be considered as Estonian overnight, that is for sure, but I'd say that any light-skinned person can get there... except for the language. Estonian language is difficult and you won't be considered as one without. I guess the rassistic note is clear but I am not going to lie to make you or myself comfortable. I don't know any dark-skinned person who is considered Estonian.
Phew! Found a new one just in time.
Can you cut the text out of the caption window before leaving? The one I saw it was appearing in chat (I think?).
In practice, binary size does not matter much for most use cases. (But for embedded and demo scene this is important)

It is a simple proxy/heuristic for the level of bloat / crust / overengineering of the runtime and to the quality of the compiler.

If a language / framework can't do an extremely simple task in an almost optimal fashion, then it is unlikely that it will improve with more difficult tasks.

It is like looking at the CPU/GPU load of an app in idle mode.
If you see your Saas remaining under 10 million revenue / annum, VC is pointless. VC businesses between 10 million to 100 million exits make no sense imo. Either go full out and sell for over 100 million or fail early under 10 million. Over 100 million is the VC sweet spot.
I'm sure the regime that supports Hezbollah and hosts international Holocaust denial conferences has a nuanced and sophisticated position on the extermination of Jewish people and is fully deserving of all the charity you are extending to them.
I can imagine that if bigfat is successful, such files will start to exist.

Imagine someone takes a bigfat drive and puts it in a non-bigfat capable machine, then zips up a directory and publishes it.

When that directory is unzipped on a bigfat machine, should the bigfat files be re-joined, or should they show as separate files? One breaks the OS file API and the unzip program might crash/fail, while the other leads to the application trying to create filenames which can't exist in the filesystem.
My work just started using https://fireflies.ai/ , no affiliation but it seems to work alright.
There's a lot of people in the community that feel this way as well but tolerate it. I think it's a certainty that whenever zig 1.0 arrives it will immediately be forked to turn the unused errors into warnings, at least for debug mode.

Another situation where I think the compiler is too eager with errors: unreachable code. A bare `@panic("")` won't compile, but you can "turn off" the error by doing `if (true) @panic("")`.
That would really only work if you owned no property or investments and had nothing but W2 income, and also no dependents.

Taxes are complicated because in reality they are actually complicated for many tax payers.
Slightly more concrete but not meaningful when those who answer self select. I read the question as "Who cares what Apple announce", without a question mark, which is emotive anyway.
True, the CL REPL is more useful than the Clojure REPL, but CL has a 20-30 year head start in development. Plus, Clojure was developed as a hosted language, and runs on .NET, Javascript, JVM, and even Dart (in-progress).

Since exceptions are quite deeply integrated into those platforms (as opposed to conditions), it has "bled through" to the Clojure APIs, and, in turn, REPL.

Folks have written a CL-style condition/restart library for Clojure (https://github.com/IGJoshua/farolero) too. https://www.youtube.com/watch?v=zp0OEDcAro0 video too.
PM as product or project?
Lot of comments here hand waving away cybersecurity attack attribution as being arbitrary or guesswork, but I think it’s important to note industry leaders like Mandiant don’t point blame lightly.

There are plenty of ways for an attacker to give clues to researchers about where they are based out of and who is funding them.
A good rule of thumb is. If it's cheap, it didn't burn too much energy! A trip to the store is purely C02 expense of almost a dollar. A dollars worth of lime, probably has C02 expense in the range of almost 10 cents.
this is just personal and professional immaturity. bonecrusher2102's empty comment does not respond to any of the arguments in the blog post. instead it's repeating the same tired prejudice that the commenter inhibits against anyone who is trying to articulate a critique of business management. i really hope bonecrusher is able to grow out of this mindset. they'd be a lot happier and more productive
As the total number of ways to accomplish a task increases it puts more burden on a programmer to recognize the usage and understand the semantic differences between the options. How many ways are there to iterate over a collection in say C++?

Libraries _can_ hide some of this, but then that might also be yet another function or operator that does the same thing. Internalizing when to use one method vs. another adds to the total cognitive load of using the language, and it takes away from the mental capacity available for the problem you are actually trying to solve.

Sometimes these differences are necessary and important, other times they are less so.
That's why the service would be so valuable! People perfectly trained to craft just the right amount of "mea culpa" and "we'll make this right" and "we're not actually lizardmen from mars".

Heck, if you had multiple clients you could even "reinforce" each other. It's so good ... I'm kind of scared it's already being done.
> Industrialized agriculture would push most people out of land (no longer need that many people), and if the people can't find alternative for living they would be even poorer.

The places where industrial agriculture has taken off, that seems not to be the story. Grandparents in China are thrilled to see their children working city jobs. It's a hard life still, but much easier than they had.

> regenerate soil, maintain biodiversity while at the same time harvest more.

I very much want those things. And corporations do sometimes make stupid decisions. But it's hard for me to believe there are such free lunches on a large scale. If there were, some enterprising soul ought to go start a business exploiting them, make a killing, put Monsanto out of business, etc.
simpler languages are easier to learn and to remember. small languages make software easier to write and to read.

complex features (in a language that does the simple things correctly) are always easily composed from the simple features available.

the antithesis of small languages is C++, which is probably the most popular language on the planet in which 0% of its users know 100% of.

with a small language, i can’t use language features which you do not understand when it comes to read my code or take over maintenance, or even understand it.
Location: Nur-Sultan, Kazakhstan
Remote: Yes
Willing to relocate: No
Technologies: Python (Django, Django REST, Flask), Rust, JavaScript/TypeScript, React.js
Résumé/CV: https://kirusfg.com/
Email: kirusfg [at] gmail [dot] com

A junior software engineer looking for an opportunity to grow professionally. Most experienced with Rust, Python, and JS/TS; have built a number of both monolithic and SOA-based Web applications. Open to any offers except for crypto/blockchain, trading, sports. The pay is of the least importance if the team/product/challenges are great.
https://twitter.com/paulnivin/status/1377079987950395393

It's fairly well known.
That's a really interesting idea, but I worry about what happens when a domain name expires and is re-registered (potentially even maliciously) by someone else.
oh, that's nice of them to "look into it". Just about all the other western nations either do taxes for the citizens or provide a free system for citizens...

a neoliberal exploitation plantation, if you can keep it...
> automatically syncing [..] corruptions [..]

This made me shudder. I used to replicate external drive A to B, in case one failed. Drive A failed by slowly corrupting file contents, which I didn't notice until a significant part of them was synced to B. Fun times.

Sync is not a synonym of backup.
The idea of looking at a handwritten note and concluding that the company cares about me specifically or that it was an actual social interaction of any significance is just so bizarre.

Maybe it's a coconut vs. peach culture thing?
Have you considered adding a dedicated `breakpoint` keyword for this use case? Linters could ignore it, but the compiler could warn or error. The problem with workarounds like `assert(0)` is that the linter lacks context to do the right thing.
Seconding Poetry. IMO it should have been the standard package manager - it just works (TM)