skysight-inc/HackerNews huggingface dataset:
Writing their own code is not mutually exclusive with open sourcing it. Arguably it might even be safer to open source it, since more eyes will be on the code looking for bugs.

Some of the biggest open source projects are owned by megacorps, like React (Facebook), TypeScript (Microsoft), and Tensorflow (Google). And it's clear from these examples that their stewardship has wrought benefits for both the company and the community. The company benefits from what would otherwise be their internal tooling becoming an industry standard - Facebook doesn't need to train React devs after hiring them. And the code is more robust as more people use it - Microsoft doesn't even need to use its latest TypeScript version, they can just wait for the community to test it for them...
Intentionally buggy commits for fame and papers (2021)
UniDep: Unified Conda and Pip dependency management via pyproject.toml
Staying consistent matters. Once I joined a new team and my first task was to take care of a large code reformat everyone was afraid of taking over. I had done a similar thing many times, a super easy thing once you know git and are focused. It turned out a terrible experience for a combination for reasons, but one important reason was that the team used merge workflow, I had always done this in rebase. Don't remember the exact details though.
That’s the same method as what we use
mini metro my beloved

and of course, mini motorways

such fun little puzzle games, I spent a good month absolutely absorbed in the latter, thought I was getting pretty skilled - only to look online and realize that there levels of strats I hadn't even considered.
I don't :/ I searched for that document for about 10 minutes and then gave up and assumed that the EU press statement was accurate.

Then somebody linked it in a comment below and then it was fairly easy as I knew what to search for from the short description in the first link.
> I don't understand. How does Firefox on desktop "break" access to some websites?

When I checked, I think there were DNS resolution failures for some domains. This was regardless of whether PIA DNS or the existing DNS servers were used. It was also regardless of whether OpenVPN or WireGuard were used, or which VPN server was used - the only pre-requisite was that the VPN be active and Firefox be used on a MacBook in particular.

It was very odd and hasn't ever happened on Windows/Linux with Firefox either, nor did happen on the MacBook with Brave afterwards either. I didn't care enough to dig into it, but some people had similar issues:

https://www.reddit.com/r/PrivateInternetAccess/comments/18nh...

https://www.reddit.com/r/PrivateInternetAccess/comments/14yl...

It seems that the suggested "fix" that worked for the other person is to disable IPv6 altogether:

> This is a bug in Firefox, you can fix it by opening about:config in Firefox and set network.dns.disableIPv6 to true

Not like it makes me like Firefox any less, it's just odd that we get super random issues like that for relatively basic use cases (albeit maybe various VPN implementations aren't necessarily that common, who knows). Would be nice to live in a world where everything "just works", though.
One 43" 4K monitor (or TV) has been my go-to for the last 4 years. Plenty of screen real estate without the physical limitations of dual monitors in different orientations. And at 43/42 inches, PPI is just right for me - no scaling necessary.
I would think they would be *if* said program was included with the system, which makes sense. The manufacturer cannot be responsible for user-supplied programs, but they surely must know what they include with their system upon install.
That explains neither the problem nor the solution!
Just a friendly recco for the Technology Connections YouTube channel. Really liked his exploration of the Coffee Machine and other vids. Not affiliated in any way.

https://youtu.be/Sp9H0MO-qS8?si=PHB0_LqfD5AArdJO
If I remember correctly earliest version of Apache also did this (though it used S/FTP instead of dropbox and .html instead of .md)
Isn't that literally just a web server?
Go on, I’ll bite: why?
I think this likely has more to have more to do with the culture of the employees at these companies than desirability.
>if you are doing anything beyond just solving the problem

It's a rant so I won't take it TOO literally, but: The opposite extreme of this philosophy is why we have stuff like Blender pre-2.7 and GIMP. There is some use to polishing up a proper looking UI and ensuring familiar UX. Especially if your audience is non-developers.

But yes, I understand. configs and CLIs should be as "dumb" as possible. Proper line breaks for readability and maybe color if needed, but there's nothing more frustrating than debugging what comes down to a bare basic command.
Yes, that would mostly fall under “aggressively prosecute companies relying on migrant workers” as I said, except for the loophole of legal migrants who lied to the US government about their age in order to get jobs like this. It does ideally disrupt employers hiring undocumented minors, but it doesn’t solve the problem of a 15 year old showing up without paperwork and obtaining employment authorization as an “18” year old and therefore passing e-verify.
Alright, so then you're NOT going to pay artists for their labor?

In the current system, artists might work for many years on a single work, or work many years perfecting their craft before anyone wants to pay for their work. Copyright gives them a way to earn money in the future that compensates them for the work they did in the past. It incentivizes creativity. Don't get me wrong, I don't think copyright is perfect, but you really ought to think more about the system you're proposing, because it's not making much sense.
This is a really good fundamentals resource: https://teachyourselfcs.com/ They list books and videos.
Ah, OK, so the end user is trying to prove there is a hard-to-reproduce fault in the software. I do not know how this is being handled in practice, but I think it would be reasonable to require evidence.
Does anyone have any anecdoctal evidence around the snappiness of VsCode with Apple Silicon? I very begrudgingly switched over from SublimeText this year (after using it as my daily driver for ~10yrs). I have a beefy 2018 MBP but VScode just drags. This is the only thing pushing me to upgrade my machine right now but I'd be bummed if there's still not a significant improvement with an m3 pro.
Show ?
> . It's pretty objectively a waste of energy, money, and time

Some would see it as saving energy, money and time because the product comes direct from the farm to the town, and you are cutting out all the middlemen (who's time you pay for and who want a profit margin), warehouses (who suck energy), long supply routes (using energy), etc.

Oddly in poorer countries, farmers markets are the cheap place to get produce, and you will pay a premium to buy from a supermarket, whereas in rich countries that trend is reversed.
So why Spotify premium and not YT premium?
I laughed, thanks :D

If there's anything to learn about humanity it's that we apply this technique in many ways.
Define short term. 120 years?

US Steel’s vertical integration practices changed the game and influence goes all the way to Apple and Tesla today.

Their way of standardizing manufacturing processes inspired Henry Fords assembly line.

Their Research Lab paved the way for the establishment of similar, famous labs at IBM, Bell, Xerox and others.

Their corporate structure set a precedent for large-scale corporations, influencing the development of conglomerates like GE to diversify various industries under a single corporate umbrella
I always say that people should treat GPTs the same way we're taught to use Wikipedia. Find what you're looking for, and then verify that it is correct.

It is not difficult to use a search engine to verify any claims that are new to you. The replies will always be constructed. And sometimes they'll even be correct.

Michael Cohen fell into a trap by not verifying legal cases that Bard was citing. They didn't exist, and he would have known that if he verified by searching the way lawyers normally do to verify these things. I'm sure his lawyer didn't verify, assuming that Cohen, as a fellow lawyer, would have done so before handing the info to him.
I landscaped with native plants that require no water beyond the rain.

It saves me a ton on water bills and lawn maintenance time & expense. As a bonus, the deer won't eat the native plants.
And also didn't it just turn out that people weren't really interested in spending a lot more money to get to where they were going a little bit faster?
2023 in Retrospective
But does that still lose the source commit long term? What I'd love to have is a mechanism that keeps references to the pre-squash commits at blame granularity, allowing one to dig deeper into the commit messages associated with a given line. Kind of like a sourcemap, but for squash instead of transpile.
Which they are likely sorely regretting as tensions flare higher with China and our navy is struggling to protect shipping around Israel.
Can we set up a system to occasionally bomb our industrial base to get these benefits?

Your point is mostly irrelevant. US steel could have innovated or even copied - but it didn't.

The idea that poor US steel couldn't compete because other startups had an advantage is assinine. That is a core message of the article itself.
Express application that converts files to HTML with pandoc and serves the results, with a dashboard.

The TODO file in the repo[1] is fascinating.

1: https://github.com/davidmerfield/Blot/blob/39d9583395c190534...
Small is under 2.5m :)

https://www.citroen.fr/ami
how often do you cut production from staging in this "gitflow light"?

in my opinion your staging/production parity needs to be really good if you do large iterations in prod, deploying smaller changes constantly will get you little oops moments more often, but you'll be able to fix them immediately since it's clear what caused it, as opposed as 2+ weeks of commits going to prod at once.

we had every feature branch create its own little minimal staging environment and started bugging developers to finish up after a week (the staging environment would tear itself down if not told to stay up explicitly via PR labels). and those feature environments went straight into main/production.
I thought it's from Alien
a funny but easy to overlooked aspect of rebase+squash+ff-only merge is that it's basically a patch based workflow in disguise

(through with some additional metadata during reviews and similar)
Current versions of Apache also do this.
> It is then given back equally to everyone.

Use it to fund the government.
Disney didn't forget :( They chose to stop, because they valued creating social change more than creating compelling content.
No worries, open source has been supporting me for 20 years, it is the least I can do.

I've been going back and forth on the trident vs the 2.4, I need to do more research on the fixed gantry vs the flying gantry but then in the meantime just browsing what is out there and I find a qidi x-max 3, easy bambu competitor, runs klipper, the company seems friendly to open source, handles eng materials, heated chamber, fast. So now I am torn as to which way I am going to go. Also the qidi is not without it's problems from what research I have done but it seems like mostly early bugs.

How do you like the v0?

Edit: forgot to add info
If you want to preserve separate commits you can just make them separate PRs?

Small PRs are better since they're easier to review.
How do people with workflows that don't do any squashing do code review? To me it always seems the main consideration deciding on commit size is about being considerate of the reviewer. Don't want to harass them with huge commits but also don't want to send barrages of tiny uncontextualized changes.
We've had a couple of big fires: https://en.wikipedia.org/wiki/Great_Boston_Fire

Somehow they didn't result in exchanging grids for winding streets.

The back bay, though, is newer than other parts of the city and it's a grid.
Re, Boston: The way I heard it was "Three rights make left, except in Boston."
Chrome won by being unethical (and continuing to do so), for a while every time you visited some Google site you were bombarded with "switch to Chrome" banners.

At the same time they often artificially slow down Firefox on Google sites (see e.g. the recent news about some code on YouTube)
Code quality is mostly related to maintainability.

A piece of code may be reliable currently, but hard to modify.
Sixty feet in dia. x 9 feet thick is about 950 yards.
Only if the web server transparently converts non-HTML sources (Markdown, Word docs, Google docs, LaTeX, image galleries) into HTML on the fly.
The US average salary is also lower than a California or New York resident but that doesn't mean the metric is bad. It simply means that ~50% of remote workers in America can move to Korea. Unfortunately, that also means ~50% of people can't. The same goes for Europe.
Mining rights are expensive.
Worse is better: This can be taken a number of ways. In terms of time (and money), "worse but I can afford it and get it today" beats "better but I can't actually get it". "Worse but easier to use" may also beat "better but harder to use". In terms of writing OSes (which was the use of C), the ability to flip bits and deal with raw memory was very useful. A safer tool might have been "better", but it also could have made it harder to write OSes.

The Fran Allen quote seems to be saying that C made all this promising research stop. Bell Labs did not have armed thugs going out pointing guns at peoples' heads. Why did the research stop, if it was so promising? Because the researchers (many, at least) decided it was less promising - or at least, that more promising options were now available. So if C did that, it did it by either showing that previous directions weren't promising, or by opening up better options. Either way, it's rather unfair to mourn the paths that were not pursued and blame C for it.
There's a grain of truth to it -- when a CPU encounters a branch it has not seen before, some CPUs (but not most modern ones: https://stackoverflow.com/a/51848422) have static prediction that assumes a backwards branch is taken and a forwards branch is not. And compilers tend to put "unlikely" execution paths past the bottom of the function so that they're not interrupting the "hot path" of the function. So if the processor uses static branch prediction, or if it hasn't executed the function before and doesn't know there's a branch there until after it's been fetched, the branch predictor is more likely to follow the "hot path" than a forwards jump that skips ahead. But yeah, static branch prediction isn't common anymore, and "likely"/"unlikely" intrinsics have more to do with tuning the optimizer than the branch predictor.
I've heard this a lot but I've never seen convincing reasoning, outside the GPU shortage era. It's also a bit laughable to call the 4060 scrawny by any means, but hey - it's not a 4090 if that's what we're marking expectations at. I'll use launch MSRP just to make comparison a bit quicker and this will raise the 4060 to $300 instead of the current $280.

Taking that down to 2010 dollars that'd give you ~$200, exactly what you need for the low end sub-model of the shiny new GTX 460. The beefy pairing of that would be the 480 at $500, or 2.5x the price for roughly 1.6x performance. The 4060 vs the 4080 has a little more than twice that performance gap at around 2.4x performance difference or 1.5x more a performance gap but the price difference is also larger with $280 vs $1200, or than 4x the price or 1.6x the price gap. In all, the gaps themselves aren't significantly different but the price of the highest tier card is what has changed. Does that make the lower tier SKU inherently scrawny and poor value for the performance? I don't think it has any relation really, but if it did I'd say it would make more sense it was the opposite.

Looking at absolute numbers one sees, just as expected, the 4060 is right in the top 3 for performance per dollar https://www.videocardbenchmark.net/gpu_value.html. This makes is hard to argue the performance took a huge dip either. It's not much faster than the same card in the previous generation, but it's also not much more expensive. Over many generations it's significantly advanced in both regards. Really the only card that was significantly faster than it's direct predecessor this generation was the 4090 and its pricing gives even more credence to the idea it's the price of the top SKU cards rising not the performance per dollar of the low tier SKUs rising that leads to the increased laddering. The other big change is you don't see cards like the 1030 coming out at launch. It's not as much that the market has stopped being served as much as integrated GPUs have come up to that level of task and anybody getting a dedicated wants something more not something the same.
agreed. It's one of the most painful parts of legacy code, especially when left 10 years ago by an engineer who has long departed the company that just says "DO NOT CHANGE" (or something to that effect). A beginner sees incompetency, while an expert can already imagine the war stories, the politics, the potential crunch and desperation, and the weeks of demonic bugs fought to warrant such a comment.

(Or you know, you dig a bit and find a thinly documented fix to that issue from 5 years ago).
This is a win for science-based energy policy.
They tried, didn't they? The move into content was forced when the content producers started pulling the licenses.
In the olden days, people took time to apply for each job. Nowadays, they spam out applications to hundreds of places in a day.

The problem is on both ends and stems from rewarding quantity over quality.
> Having water for individual people free for basic personal use wouldn't be a problem.

Operating the water system to deliver water is expensive. If you want to put out a rain barrel and collect rain, it's free.
Rebasing would be so much better if Git just had better defaults.

Having to fix the same merge conflict for each of your commits is one of the leading causes of developer burnout :D
Underrated new book not mentioned here - Think Like a CTO by Alan Williamson
> Does ZFS support transactional reading and writing?

I don't know that I understand your question. ZFS supports POSIX transactional semantics, which is not ACID, though ZFS's design could support ACID.

> Is that just the traditional transaction log + btree update approach most databases used?

Basically, yes. The idea is to write a sequential log of a) data blocks, b) metadata operations (e.g., renames) to support fast crash recovery. During normal operation ZFS keeps in-memory data structures up to date but delays writing new tree transactions so as to amortize write magnification. On unclean shutdown ZFS checks that all transactions recorded in the ZIL have been written to the tree or else it will do it by a) rewinding the ZFS state to the newest fully-written transaction, b) loading the contents of the ZIL from that point forward.

Because the ZIL was designed at a time when fast flash devices were expensive, it's really a separate thing from the rest of the tree. If one were to start over one might integrate the ZIL with the rest of the system more tightly so as to further minimize write magnification (e.g., data blocks written to the ZIL need not be re-written to the tree).
You've just reminded me that o reilly used to publish quite a lot of cookbooks, I think there was a bash one, perl, python etc. That kind of book would probably be quite useful for getting advanced concepts I guess as a lot of more advanced books are quite abstract.
Hasidic Jews' Battle with the Internet [video]
Lol, my biggest gripe is that these recent posts are showing all these amazing things that we won't be able to enjoy for quite some time.
It makes them harder to get excited about.
That sounds like a bad CTO.
Folks looking at this may also be interested in similar visa programs offered in east/southeast asia for context: Thailand, Malaysia, Indonesia, Singapore, Taiwan.

Singapore's requirements strike me as especially conservative in comparison (five years leading a co with $30M raised, and that's just one of the "two of three" reqs).

I'd also look at the local tech ecosystem before applying -- Twitch is shutting down in South Korea in 2024 due to sender-pays "network usage fees" in the local Telecommunications Business Act. Also there's legacy technology (esp for online banking) that depends on Internet Explorer and ActiveX due to a home-grown encryption standard built in response to US Export Controls limiting 1990s browsers to 40-bit RC2/RC4, so Windows is still the predominant desktop operating system there.
I never recall sewing my own patches (thanks mom!) but I like sewing today, mostly to repair clothing, which gives me an absurd amount of satisfaction. It occurs to me that it should have been one of the very first merit badges a scout earned: sew ur own patches.
That’s why most folks recommend poetry or anything else made in the past decade. pip can work, it just doesn’t have sane (for 2020s) defaults.
If you're using an Intel Mac at this point, you should 100% upgrade. The performance of the MX chips blows away the Intel chips and there's almost no friction with the arm architecture at this point.

I don't use VSCode but most of my team do and I frequently pair with them. Never noticed it to be anything other than very snappy. They all have M1s or up (I am the author of this post, so the detail about their hardware is in the link).
You might want to read up on Clotaire Rapaile, who is the de facto father of the modern SUV and record margins per vehicle for american auto brands.

One could argue quackery but this is C-level paying millions in consultancy fees quackery.

"Rapaille no longer sees patients. He doesn't need to, because he's paid well to supply his insights to corporate America - and lives in baronial splendor outside of New York City.

Apart from Ford, GM and Chrysler, he's advised companies like Kelloggs, Kraft, and Proctor & Gamble. They pay him to get inside the deepest recesses of our brains. In fact, he's known as the "car shrink" in Detroit." [0]

"The notion of need is very, very interesting. Because what do we really need, you see? I need food, I need water. I need shelter," says Rapaille. "And you know that, but then there are other needs, needs of identity. Needs of communication. Needs of being loved, being respected."[0]

"Why do you buy a car that doesn't even make 10 miles per gallon, doesn't fit into your garage? Do you really need that? And you don't need that intellectually," he says. "But at [...] the deepest part of you, the gut level if you want, you feel like you need that."[0]

"I don't believe what people say. They have a good alibi. They have a way to explain things to make them feel comfortable about what they're to do anyways," says Rapaille, who believes it's now considered hip to appear ready to take on anything.[0]

[0] https://www.cbsnews.com/news/the-thrill-of-the-suv/
A Macbook-equivalent AWS instance prices to at least the cost of a Macbook per year.
I use a home video appliance called camect which is accessed through a web interface which explicitly only works in chromium browsers. Oddly, I often find that the bbc news page doesn't load images on the first attempt in Firefox, but always does in Chrome.
Full AACSess: Exposing and exploiting AACSv2 UHD DRM for your viewing pleasure [video]
I think the parent was thinking of the US. There, natural gas is an abundant predictable, and cheap base energy source. Not so much in Europe. In Sweden the mix is nuclear, water, and the rest, but we're still suffering from the rest of Europe not having a cheap base alternative, since the markets are interconnected.
Europe would _love_ to have it's own natural gas source right about now.
I’ve noticed more of laces don’t even ask “Is Pepsi ok?” which might be where things start to fall apart.