skysight-inc/HackerNews huggingface dataset:
I think the main issues with postdoc even if it’s enjoyable is that there is an expiry date to how long one can postdoc.

Even if you enjoy postdoc, some places won’t let you stay for more than 4 or 5 years.

If permanent postdoc positions existed, I am sure many people would view it favourably, especially if the lab is a good environment.
... are we no longer doing 'works on my machine' ?
Thats clean! maybe more onversational inputs can make it even better.
good resources:

1) https://trunkbaseddevelopment.com/monorepos/

2) and (but I don't know it as well) https://monorepo.tools/
They are silver bullets -- really, golden geese -- that are fixing it all, as fast as we spend to build them out. We could be building out much faster, if not for societal inertia and corrupt lobbying.

Each dollar spent on nukes is a dollar not spent on radically more productive renewables. Thus, each diverted to nukes brings climate catastrophe nearer.
That’s why you make it a legal requirement- if Qualcomm wants customers it has to comply.
> You either place faith on a build step working deterministically when it was not designed to work like that

I'm sorry, what? Why would a build not work deterministically?

> If you decide to put faith on your ability to run deterministic builds with a potentially non-deterministic system

If your build is non-deterministic, how can you have any faith in the binaries it produces? You would have much larger problems in that case.

> You use git to track changes, regardless of where they came from

You probably don't want to do that if it is 70% of your codebase and slows down all your developer's git.

> Then you need to have internationalization test steps for each localization running as part of your integration tests to verify if your build worked

I'm convinced you've never used a build system before. Your build should fail if required files are missing. Downloading translation files at build time from some artefact repository vs storing them in git is how a lot of companies do it.
Ask HN: Will higher fuel costs even the playing field for retail against amazon?
Due to higher shipping costs?
Yes, but on the other hand, ...
You may want to set the '-diff' attribute for these files so that git will not show diffs for these, instead it will show 'Binary files differ'.

There is also '-merge', which will cause git to not attempt to merge the contents, but just ask you to pick a side.

The challenge however is then verifying the contents of these files in things like merge requests.

See https://gitirc.eu/gitattributes.html
New open source audio plugin format from u-he and bitwig
Microsoft is starting to port VS studio (IntelliSense) which is proprietary to VS code which is opensource.

Current C# plugin (Omnisharp) is opensource, so they announce that it will be replaced by a closed source selector that let you choose the opensource or the proprietary plugin with the proprietary as default.

It's Embrace, Extend, Extinguish just in front of our eyes, so opensource people are pissed.
I wonder if more those accounts have pro and can see you viewed them recently, probably multiple accounts are owned by the same groups so when they get a report on a bunch of posts they simple map "who looked at both profiles".
Which portion?
Claiming that part of Darwin is opensource, which it was, is not quite the same thing as claiming to love opensource, and yet slowly close it up once you have mindshare like with VSCode.

Apple didn't take ownership and then start closing CUPS, but they have also never pretended to be a friend of OpenSouce. They haven't produced anything opensource since then.
There have been a couple of projects, like their rebranding of KHTML that suited their purposes but they never donated time or money back, or even pretended to help upstream.

If you look at the Asahi Linux on M processors, Apple don't hinder and may have arguably done things in a way to not block them but they certainly have not helped or even claimed that it was a good thing.
What are we supposed to do, burn his books? The man is dead.
"Trying to do consistent, smooth lines using a round brush? Good luck."

It just takes practice. As long as it is the proper size for the line you are making and it holds a decent point, though, it isn't so much of an issue. Rigger brushes are long-bristled, thin, and round and used for lines, after all.
I don't understand the logic of combining microservices with a monorepo. The whole point of microservices is that you don't care what is beyond the external contract of the service. Who cares how each individual team decides to name their stuff. Why do microservice teams need to care about having every single service checked out? Who or what would be bulk applying changes to all services? This is madness.
I agree, but I'd also like to defend Jackson on this one. He was brought in after Del Toro dropped out and the movies had been in production for years already. He had no prep time and seemed to exist on little sleep for years. You can see some of this in the behind the scenes recordings/interviews they did. I have a feeling they were only as good as they were because of him. Regardless, they were disappointing.
LinkedIn is closer to Facebook imo. The subreddit /r/linkedinlunatics is pretty funny, and also a bit scary.

It's pretty interesting actually, on facebook you see people show off a manufactured persona that is always laughing, on vacation in exotic or glammy places, and on LinkedIn it's the exact same phenomena but the success indicators are different.

I'm still a bit clueless on the whole LinkedIn influencer thing though. Is there some monetary gain from that? I don't think they have the same possibilities for eg ad space or sponsorship as eg youtube or blog influencers, so perhaps it's more a personal vanity thing, or selling books and courses.

</rambling>
Personally I like sell-outs, writers who aim to please and are complete morons. It's schlock and I love it. In fat, i'm thinking of paying imbeciles who can't write to write me something so I can enjoy it's utter blandness, incompetence and naivete
In most developed countries the "legal concerns" of an employer include knowing basic details about who they are doing business with.
Resources for learning about decentralized technology development
I'd like to learn more about building decentralize/distributed systems technologies (web 3 possibly). I specifically am interested in the development side of things. Can one point me to resources for learning this stuff in this regard?
here's the link to the status page since the posted link just goes to their homepage https://status.heroku.com/
With Russia fielding hypersonic weapons now, could you imagine if they threaten the US with "Send arms to Ukraine, we sink your aircraft carriers"? In that sense, hypersonic missiles may replace much more costly to maintain and much harder to deploy nuclear weapons.

In fact, it looks like the US has 11 active aircraft carriers [1]. It seems that they are all near port right now [2], this might be the reason.

[1] https://en.wikipedia.org/wiki/List_of_aircraft_carriers_of_t...
[2] https://www.marinevesseltraffic.com/vessels/USS-George-H.W.-...
both cabal and stack have improved, there's now a pretty good language server in HLS, there's ghcup to download and install both GHC and tooling and manage it (both on linux and on windows). And for quick one-off experiments I usually use nix (I don't fully use it, too complex for my brain, but being able to do

nix-shell -p 'haskell.packages.ghc{version).ghcWithPackages (pkgs: with pkgs; [any number of packages here])'

is just an insane superpower that lets me experiment stuff in ways that most other ecosystems would dream of)
Yep, they saw no real backlash to doing this for the Python one, then decided to do it here as well.
apt updates are not transactional, so abort the update mid way and you have a partially applied update. Hopefully the packager was careful enough to ensure your system still boots and reapplying the update cleans everything up.
> Companies are not interested in the candidate, but in the amount of money a candidate can generate for them.

> And in a business you optimize for profit.

This is why it's in the employer's best interest to say that you're family, or that loyalty is a virtue. It makes it easier to low-ball your salary and keep it from rising too much.
Note that colors we can perceive aren’t all in the rainbow.
There’s no pink in the rainbow. That’s because pink is what is left when you take white light and remove the green part. It’s minus green. There’s no wavelength that corresponds to pink.
Well, I don't really think this would be considered truly evil except by the likes of Stallman.

They wanted to make an awesome plugin to C#, they chose to do it closed source to extend their vscode moat. It's quite corporate of them, but i still get their point.
They have “hundreds of developers.” It seems completely reasonable for them to have a team focused on DX. It’s one of my most common recommendations for rapidly-growing companies, which are often focused on features at the expense of productivity. A DX team is one of the lowest-hanging fruits for fixing the problems that causes.

(Improved testing practices is often second, but that’s not a low-hanging fruit. It’s a big, juicy fruit that’s waaaaay up in the canopy. And then comes joint product decision-making within the team, which may as well be on another planet entirely.)
Bank cards: where have all the numbers gone?
I understand the historical/military circumstance. None of that changes that China does _not_ have to fight.
Chile does not drive massive energy projects. China is in the driver seat.

I doubt it will end up built, but that will not be because it is impractical. It will be because local generation and storage will turn out to be cheaper and less vulnerable to geopolitical upset.
author here, xlf files are translations that are coupled with the texts we set in the code so they're not really generated I admit that was misleading. What I wanted to get across is they're not touched directly by engineers but they're still created through our translation pipeline where real humans translate them
Microsoft can't have it both ways. Crippling open tooling in order to extract more revenue or drive lock-in will undermine their efforts to make .NET relevant outside of the niche occupied by traditional .NET shops.

I can't imagine that there's a business justification for this decision that is compelling enough to offset the long-term damage to .NET adoption and community trust.
> whole confusion around reason/rescript may have harmed development of ocaml for a while

OCaml is an anchor language for many important projects (e.g. Coq) and companies (INRIA, Janestreet etc). The momentum behind OCaml has grown and I don't think the rescript/reason separation affected it _that_ much.

But I am curious to know if rescript/reason issue harmed rescript. While rescript gained a lot of technical freedom from the breakaway from OCaml it lost some people along the way. Was the breakaway worth it in retrospect?
Loved by developers how? Because they own Macbooks?
Why would I want to limit myself with particular diets for weight loss when I can just cut calories and eat everything I want.
Recon is very valuable. Cannons are far more effective if you know where to point them.
You can do a lot more with liquid capital than options. Guaranteed money is worth more than maybe money, especially if you have a family.

If you truly believe they're valuable, then invest when they ipo.
> We aren't in this mess just because China is supposedly a bad guy, there are real relevant historical reasons why things are the way they are, and they can't be swept under a rug.

If China attacks Taiwan, it is absolutely because of China. It would, after all, but their own choice to engage in such a war of aggression.
They did kind of head that way in the early days of OSX, to try to bootstrap a development community by being close enough to Linux to make it easy enough to switch. I'd probably characterise them as having an abusive relationship with Open source.
What would be a better structure?
Wouldn't happen if Vscode was GPL. Which of course MS would never have done either, of course.
You could however reasonably expect that core tools like debugger and LSP will be open too.
Padlet (YC W13) is hiring in SF to build software for a good education
And, all more expensive to operate than alternative methods.

Which is why nukes are today uncompetitive, and get less so every day. The cost to build all those nukes would build far more renewable generating capacity and storage, far more than we will need. So, we will instead spend far less and get all the power we need. Existing nukes will shortly be too expensive to continue operating, and will be mothballed. Their eventual dismantling will consume a not insubstantial fraction of our much reduced energy budget.
drivers, as you said, for filesystems for instance,
syscalls available that we know and love :),
somewhat easier deployment (elf instead of raw bin),
other abstractions that linux provides,
multiprocessing (if done carefully),
real multithreading,
While Swift might be open source - to effectively do something with it you still need to buy a Macbook or even iPhone, which as we know are expensive.

To release any application in Apple ecosystem you have to pay for developer account each year. You might play around with stuff - but I don't believe anyone would be developing on their platform just for fun.

Microsoft gives stuff away for free - loads of stuff - there is much more people who will play/try out/start some projects with free stuff. But then the more people the easier is to see ones that are not happy and would like more. Then this mass of people is active on multiple forums, not only on .NET dev subreddits.
> If you're doing much beyond simple crud, I imagine you're going to want a lot of what you're describing fairly quickly.

There are different models for asynchronous execution across different systems. Even then, Rust isn’t a silver bullet.

A request can be scoped to a single thread, and then messages can passed across systems (queues, pubsub, etc), stored to a database, etc etc.

Not having concurrency within a single process doesn’t mean someone is doing simple CRUD, unless you’ve mistaken Facebook.com, Twitter, and Amazon retail website to all be simple CRUD applications.

Rust seems like a solution for your very specific use case, or it’s better suited for C++ and systems programming scenarios.

The borrow checker is a pain in the ass to use. Presenting Rust as silver bullet and ignoring its cost is misguided and near sighted at best. It’s not just Rust but saying <X> is the perfect solution is generally wrong. Every thing has a cost.
Worth pointing out that VS Code is not really open source.

The builds are proprietary.

It’s based on an open source core but the builds can include anything that Microsoft thinks will be commercially useful to it.
The LSP situation with Python was very frustrating, because it totally breathes the oxygen out of "proper" OSS implementations.

I feel like with a _loooot_ of coordination it should be possible to have proper, open source LSP implementations that are very performant. Mainly a question of finding enough people willing to fund this work, because it's definitely work!

I personally also have gripes about ending up with some JS thing to do constant parsing and processing of files.... but I don't have anything to back it up.
Suitable:

Anything with a write-based working set that fits in the buffers of the primary instance;

Databases that are unused most of the time;

Databases with a lot of read replicas (potentially with Neon only providing the read replicas, not the write node/hot standby);

Apps that want to run analytics on the data, but don't want to transfer O(datasize) data to a different DB every time, and also don't want to deal with the problems of long-running transactions.

Not very suitable:

OLTP with writeset that doesn't fit in the caches;

Databases that need <1ms commit latency.
I guess it's "brand-building", be it just for the sake of ego or as a funnel to their other channels.
I'm sure if Ukraine had spent some money on "peace research" in 2013-2021, this whole mess could have been prevented.
/s
Thx for your insights!
Interesting. Thank you for that explanation. That makes a lot of sense.
Not explicitly about the article, but the title font is waaaaaaay too big on mobile. I have a decent sized phone (galaxy s21+) and I still have to scroll to get to the start of the article because the title itself takes up the entire viewport on load
Basically yeah - you can show off that you are working in rich company (so by association you know who is making that sweet $$$$) because you have a new Macbook for dev work.
Even real life twins don’t exactly match. No digitization process can be error free, the “digital twin” language is to indicate that it’s supposed to be a realistic model rather than an editorialized/interpreted environment.
Interesting to me is

1) How the article focuses entirely on fossil fuel consumption rather than something much more damaging, like housing

2) The author's key takeaway is this is great and we should use it to manipulate people into consuming less fossil fuels by making their usage punishingly expensive.

In particular, 1) is a societal wrecking ball, because no home means no stable environment to raise children, means more trouble in the pipeline for the next generation. Many people in the generation won't even have children and others will have fewer than replacement rate. 2) makes me think the same sort of people are behind the housing crisis. They believe in overpopulation and therefore they want to curtail it by making housing punishingly expensive.
I can definitely say that for me, this is the straw that breaks the camel's back. I am turning my back on the .NET ecosystem, after having written C# for 7 years. The `dotnet watch` debacle from last year, still having key parts like the debugger closed-source and now again with this: It's just too much.

I do not want to build anything of value on top of such a shady platform that's completely controlled by one Megacorporation. It's too big of a risk.

No matter how many MVPs tout "MS <3 Open Source", how can anyone still believe them after these repeated violations?
>It is clear that natural selection exists, but it looks like there is no space for chance in evolutionary science

I've always assumed it's because evolution requires something happening thousands of times. The more events that are included in something, the less impact chance can have.
Yeah, this sounds more like a pile of technical debt attached to a competent business.
Super PACs / "independent expenditures" are probably a big part of it. Revolving doors are probably another important mechanism (which allows to bribe people as long as the payment is delayed until after the bribe-receiver quits their job).

Another mechanism that may be important is bribing people by paying their family members (hiring them as lobbyists, investing in their companies etc.).
A problem of the .NET ecosystem is that there is no open source debugger for C#. The Microsoft-provided debugger has strict license terms that only allow it to be used in Visual Studio and Visual Studio Code.

JetBrains needed to write their own debugger for their cross-platform IDE Rider. Luckily they already knew a lot about .NET to do this and it turned out very well but it's still not the official debugger and also not open source.
Sustainable and optimal are different. For a company like Microsoft at least.
I suppose the question I would ask you is: why do you need it to be a fiction?

Why can’t you just… make it a new reality?
> But if we use ORMs, they're "services" we can swap, right? Sort of?

That's the dream, but often the answer is "no, not even sort of".

Plenty of companies with super smart and experienced engineers laying the DB foundations for a company early in its life have failed at this goal. A few problems come into effect, two immediately spring to mind:

1. Eventually some engineer comes along with a reasonably compelling business case to either pass by the abstraction layer, or extend it so that it's no longer general (e.g. now it only works for Postgres).

2. As the company scales Hyrum's law comes into effect and a thousand pieces of code come to have subtle dependencies on implementation details of the DB.

(2) is particularly hard to avoid because DBs are often at least the nominal source of performance bottlenecks and engineers will do almost anything to make performance acceptable no matter how horribly it wrecks abstraction layers.
Or four, as suggested by the top comment: Linkedin pro and correlating "who viewed all of my reported accounts recently?"
Someone once said "Startups don't die, they commit suicide".

I was working on a small bootstrapped product for some 3 years. I had great opportunity at the time, because I was still young and living with my parents and I didn't have to work for money at the time. I got some pushback after launch, but I was tired of the sacrifice and started freelancing and moved out to live on my own. I never formally declared that I quit, I just thought that I would do it in my off time. I had little imagination that this would practically meant that I'm quitting because I was not getting anything done with that approach. 2 years later, I decided to get back to it again. I started laying low, go back to living with my parents (this time I did earn money though), but I unlocked some 40h/week for my product experiments. After some 6 months of experimenting with the old idea and realizing of how horrible the code was, deciding to rewrite it from scratch, I came upon a related, but different idea that I have found actually to be useful myself and I saw just how superior it was to the previous idea and how it solved pretty much every problem with the old product. I also made many mistakes with the old product launch, that was just due to being too inexperienced (being too greedy with the price, not marketing to enough people - and of course, giving up way too quick).

I'm still working on the new product. Not sure if it will succeed in any way but I do not want to lose momentum. I'm learning tons. While working on the current idea, I have 2 new ideas for bigger products. I guess if it fails I will try the VC route with something new. BUT do I wish I could go back in time to the time when I stopped, I would be 2 years ahead and likely launching the new product now.

My story is of someone who did not succeed yet. If I persist and not die too soon (like literally die), my story will fall under "survivorship bias".
Real-time S-tier wallet watcher (buy,sell,mint and burn)