skysight-inc/HackerNews huggingface dataset:
You say that like real-time multiplayer gaming doesn't exist or something. Both of them have worked on those.... I think Carmack invented a lot of the techniques we use for those.

Yeah sure, the scale is smaller, but you can't get away with making the user wait 10 seconds to render text and images to a screen either. I think the software world might be a lot better place if more developers thought like game developers.
I actually use ripgrep.

But modules can be in different repositories I haven't cloned yet.
I'm unsure how to "sell" this idea. I don't want to force my view on others until I truly understand the problem that they're trying to solve with modules/microservices.

For searching multiple files, ripgrep works really well in neovim :)

[1] https://github.com/BurntSushi/ripgrep
> The python maintainers went out of their way to break things - and were smug about it. That’s what it felt like to the community.

The other side of that coin is that the python maintainers went out of their way to push back the Python 2 EOL. They kept on pushing the date back and back again, as per the sunset page:

"We did not want to hurt the people using Python 2. So, in 2008, we announced that we would sunset Python 2 in 2015, and asked people to upgrade before then. Some did, but many did not. So, in 2014, we extended that sunset till 2020."

The drawn out demise of Python 2 was, frankly, painful.

I have no time for whinging snowflakes complaining 12 years (2020-2008) was not enough time to migrate their code to Python 3. Hell, even the original 7 years (2015-2008) should have been long enough for 99.999999% of the community.
> Anything I publish on any social network I'd be also comfortable seeing posted on every wall in foot-tall letters, with my real name attached to it.

You misunderstand. It's layered defense / minimizing exposure. Nobody is suggesting it can't be done, but it not going to be normalized in the current Fediverse, and most potential attackers do not care enough to build throw own search engine.

The main reason is quite clearly stated in the article, and I'm not sure if you didn't see it or just don't care because you're not affected.

> And, if you’re vulnerable, attack you, shame you, doxx you, SWAT you, try to kill you.

A lot of people that are being targeted by the likes of KF or Libs of Tik Tok find nice comfortable corners on the Fedivserse because they're not immediately discoverable by someone typing their name into Google.
grep can search multiple files. Tags can jump between files.

LaTeX is an obvious case: why pay to recompile the whole huge project, for each tiny change?
Not sure what displeased him about this law, but last I checked, he was one of the most environment-minded US presidents, famously creating the Environment Protection Agency ?
And of course it's lot easier to read 200k+ LoC shattered around twenty repos.
The word came from a specific [1] event, people were not getting randomly thrown out of windows.

[1] https://en.wikipedia.org/wiki/Defenestrations_of_Prague
Microsoft don't have any generically extensible binary format that they use consistently, like Google does with protobufs. Besides, XML isn't so bad.

Look at the alternative: Apple went with a generic binary config format for macOS (binary plists) but then introduced an XML version anyway. As an industry we've never got any good at managing the dichotomy between efficient-for-machines binary formats and efficient-for-humans text formats.
I’m surprised none of the big 3 cloud providers have come out with a cloud native language where modules or even classes gets deployed as micro services that scales horizontally.

Then you can have a mono repo that deploys to multiple micro services / cloud functions / lambdas as needed depending on code changes and programmers don’t have to worry about RPC or json when communicating between modules and can just call the damn function normally.
- Name: Ryan Brammen
- Jobs: Technical Product/Project/Program Manager. 13+ years
- experience in finance, fintech, healthcare tech, and
straight tech.
- Linkedin: https://www.linkedin.com/in/ryanbrammen/
- Location: Dallas, TX
- Remote: Yes, preferred
- Willing to relocate: Yes
- Technologoes: SQL / JavaScript / Apps Script / Snowflake /
Tableau / Database Administration/ Atlassian (JIRA /
Confluence) / Microsoft Suite / G-Suite
- Resume: https://drive.google.com/file/d/1ETu3iNDSqQ9qXKJoMcVcq49k2E1Dir_b/view?usp=sharing
- Email: ryanbrammen@gmail.com
Noteworthy Deep Learning Papers of 2022
> This is totally false - code produced by 2to3 no longer ran on 2.

That's what "breaking changes" and "backwards incompatible" means.

What exactly is hard to grasp?

> So you ended up w a chicken and egg problem.

You really don't. Your code and your upstream dependencies need to be ported to python3. Once your dependencies are updated, all that's missing is you doing your job.

Python2 has been on the path to deprecation for how long? A decade?

You're fabricating problems where there are none.

> Your comment is a perfect illustration of the issues. Lots of user blaming.

There is no issue. When I had to port projects to Python3, I just ported them. No drama, no hangup. You're pretending there were problems where there were none, and you're throwing a tantrum when this fact is pointed out to you.

There is really no justification for this. It's high time people like you stop making up excuses and start to own up their misconceptions, misjudgements, and mistakes.

Some projects were rewritten from scratch in entirely different tech stacks in less time the likes of you complained they could not update their projects from python2 to python3.
Well, from my point of view, regulating has never gone well. There are all kinds of example that can be cited, often called "unintended consequences" which I believe are not actually unintended at all

Government: If you think you have problems now, wait until you see our solutions
I'm inbetween. 10K line files are usually extremely messy, but they can be written not to - a large number of well-organized, well-capsulated <100 LOC classes can be very readable if smashed together in one file. It just so happens that people who tend to write readable self-contained classes just don't put them in 10 KLOC files, but rather split them. And vice-versa, creating an association "10 KLOC files are unreadable", where it's not the length of the file, but rather the organization itself.

Same for business logic - very clear separation can be cumbersome sometimes, but otherwise it becomes messy if you're not careful. And careful people just tend to separate it.
Just one of many reasons: parallel compilation.
Isn't the cache situation somewhat solved via defining your RPC as either a "query" or "mutation" (for example in systems such as https://trpc.io/ > https://trpc.io/docs/caching)?
This will eventually solve the house shortage! In 60 years there will be a major surplus. I wonder how JP Morgan factors in real estate collapse during that time.
also involved the winemaking and vineyard biz (east coast us). i think that estimate is on the lower end, but also per season (single harvest per year). while the vines do take 5 years to really start producing, they will continue to produce for decades after, with a cyclical nature of peaks and valleys approx every 5 years. $10/per plant seems very low, even if selling only as u-pick. also highly depends on your spacing and grape type.
for us in the south east, muscadine grapes are enormous and a single plant with a 12' spread can produce quite a lot per plant at its peak, easily 80lbs of grapes in one season. wine is approx 15-20lbs grapes per gallon from that.
compare https://www.visualcapitalist.com/u-s-share-of-global-economy...

Absent another series of wars in which everyone else conveniently bombs their infrastructure to rubble twice over, I see no pathway to return to 40% nominal share for the US.
You want Elixir and Erlang/OTP process trees, not Microservices.
I think what goes wrong with dividing is people truly just splitting the code into multiple files.

I think the code should be split conceptually thus not just copy/paste part of code from main file to submodules, but split the code around some functional bounderies or concepts so that each file is doing one thing and compose those concepts into more abstract concepts.

So that when I try to debug something I can decide where I want to zoom in and thus be able to quickly identify the needed files.
Mathematicians rarely collaborate by forking and improving other papers. They rewrite from scratch, because communicating ideas isn't considered the important part, getting credit for a new paper is.
I mean, the argument is essentially one of "sure, he may have been completely awful, but it all worked out so, if we assume that's the reason things worked out (ignoring the myriad other factors and pure luck) then we suppose that, however they had acted or the damage caused, they were right to do so. The ends justify the means - even if we can't tell for sure or not that by those awful means we arrived at those desired ends."

Frankly, it's ex post facto justification by false entailment. I don't buy it.
... then before you know it your code-base is 10 million lines long and you have no idea where anything is, what the side-effects of calling X are, what's been deprecated, onboarding is a nightmare, retention of staff is difficult, etc. You may be right for the smallest of applications, or whilst you're building an MVP, but if your application does anything substantial and has to live forever (a web app, for example), then you will have to get organised.
Tip: if anyone brings up "Minders, Finders, and Grinders"... than ponder which one they think you are... There is zero respect in some firms. =)
The problem with it being many many moons ago is that C++ has evolved so much since then that that course is now so outdated it's pretty much irrelevant.
Ahh got it. No, HAOS features a full HA installation including the UI which is then of course also accessible via the Raspberry Pi and an attached display :)
Symbolic regression which involves a ton of CPU-intensive mathematical operations, but Numba is very picky on what it will or won't optimize.
i really dont think it could .. if you pick a few random users and check their rating curves on lichess it doesnt take long to see that for many, their best rating was at some point in the past. i think this is because their interest in chess wanes over time and they lose rating rather than because their intelligence is decreasing.

i think users that fixate on chess as an intelligence test risk misattributing their performance to their capacity because they do not understand all the factors of performance.
Go is not statically typed, really. Consider using Haskell, if not Agda.

About "type-related programming bugs." I once took endeavour to write cycle-accurate MIPS CPU simulation in Haskell. Most of the errors I uncovered were easily preventable with the types - mark integers with their size in bits and you will never add instruction pointer to an unaligned offset. Haskell did not had proper types at the time but later I used that trick quite successfully.

With the types you can eliminate whole classes of logic errors. They just will not appear before end user.
The problem arises when you need to read the code of other modules or services. If you can rely on them working as they should, and interact with them using their well-defined and correctly-behaving interfaces, you won't need to read the code.

I'm a proponent of keeping things in a monolith as long as possible. Break code into files. Organize files into modules. A time may come when you need to separate out services. Often, people break things out too early, and don't spend enough effort on thinking how to break things up or on the interfaces.
Boston Harbor was a dumping ground in living memory. There were industrial sites along the Charles, which empties into the harbor. Sewage went right into the water. Trash was dumped there. It was toxic.

You can now catch bluefish, see harbor seals, and even spot whales within sight of skyscrapers. https://www.boston.com/news/local-news/2022/08/01/humpback-w...

One of my favorite transformations: Spectacle Island, which doubled in size after being used as a city dump from the 1920s until 1959, is now a national park.

https://www.bostonharborislands.org/spectacle-island/

https://www.nps.gov/places/spectacle-island.htm
Honest question: do you think the same exact 10+K lines of code are easier to read spread across 1,000 files? And why do you think the overhead of maintaining the extra code for module boundaries is worth it?

EDIT: And what editor do you use? I'm wondering if a lot of these differences come down to IDEs haha
This is a good idea. Most modern languages have their own build tool which handle most of these things, so this requires some separate learning with C++.

Some ideas for a curriculum:

Context

- C++ as a standard, compilers as implementations

- a build tool's role in handling compilation and linking

- compilers having limited abilities, having limited warnings and analysis by default

Build tools

- evolution: e.g. make -> autotools, cmake, meson

- focus on meson as the build tool of choice (personally I'd avoid CMake since it has a lot of legacy baggage)

Testing

- gtest/gmock

- catch

- designing for testing

Analysis tools

- why you should care: security, catching bugs

- cranking up built-in compiler warnings to reasonable standards

- external tools like clang-tidy, cppcheck

- sanitizers: address sanitizer, leak, thread, etc.

- fuzzing

Dependency management (probably the toughest, since it's still a mess)

- history: usually just relying on system packages, or installing libraries globally from source

- Conan (probably the best option for simple dependencies that's actually catching on)

- CMake external projects, Git submodules

- Docker

- Nix (if you're feeling adventurous)
I spent 10 of my most formative years on St. Thomas. My adopted father and extended family were very involved in the government there. The corruption is almost unparalleled in both its quantity and blatancy. Hopefully this firing will shine some light on the relationship the governor had with Epstein.
How a lib where you don't even know whether it computes correct results can be called "best"?

Only because something spits out numbers really fast doesn't say anything about the quality of this something. Especially when considering that optimizing for speed comes most times with very hacky code! This, plus the fact that this code is usually written by laymen (scientist aren't software engineers!) makes such things very questionable.

After looking into scientific computing and the usual software "quality" there I lost quite some trust in anything that comes out of there. This was actually very disillusionary and extremely sad to find out. This could even destroy the broader trust in science in general (as everything today in this field depends on statistics calculated by computers). This would be an catastrophic outcome! But most people would currently even deny the existence of an issue…

Related (together with the parent): https://news.ycombinator.com/item?id=34224186

Also related as people (scientists!) got blinded by the promise of speed without considering correctness:

https://yuri.is/not-julia/

A house of cards… :-(
For an alternative solution, describe the directed graph by listing the nodes and using whitespace to represent the arcs:

$ cat riddle
Vixen Rudolph
Vixen Prancer
Vixen Dasher
Dancer Vixen
Comet Vixen
...
Vixen Dasher

Then use tsort:

$ tsort riddle
Dancer
Donder
Comet
Vixen
Blitzen
Dasher
Rudolph
Cupid
Prancer
Fair enough, though I've been working as a programmer for over 6 years now (and I've been programming on and off, as a hobby, for over 3 decades).
Unfortunately the linked UI is in an endless loop on my side and won't open :/ Yup the plan was to buy a (used) table which can also be disassembled to take a look inside and place the sensors where they need to be :) Fortunately they are not that pricey.
Counter point - https://github.com/microsoft/TypeScript/blob/main/src/compil... - your task is to just make it a little bit faster. Where do you begin with a 2.65mb source file?

It’s easy to miss the point of what the OP is saying here and get distracted by the fact this file is ridiculously huge. This file used to be a paltry 1k file, a 10k file, a 20k SLOC file… but it is where it is today because of the OP suggested approach.
His trans critiques are very reasonable though, particularly when he talks about males in women's sports, males in women's prisons, and the social contagion aspect of this type of identity.

These are the questions that cut across the entire political spectrum, as there are plenty on the left questioning the excesses of this activist movement too.
May any real or hypothetical deity you might believe in bless you :-)

Thanks!
You don’t have to necessarily decide one way or the other. I have systems where the decision to put the module in the same process or to call it via RPC is done at runtime. Java’s dynamic proxies help with this, but it can be done in any language. The only downside is that one has to think about the size of messages crossing the API and that they need to be immutable values, not references to something in the process.
I have no problem running stuff from a decade ago either on the same box and installation that it was on a decade ago. But virtual environments and pip freeze are closer to mothballing an old box than displaying long term code compatibility and functionality. Their main reason to exist is as a workaround precisely because there are such issues.

The whole idea that you need a multitude of environments to support applications written in the same interpreted language is where it breaks, that should not have been necessary if backwards compatibility had not been an issue.
It won’t stop people from bullying, just reduce the amount of integrated time a bully has access to victims.

It’s an obvious solution that would work to some extent.

Bullies don’t deserve the right to be at school when they could learn online if they are pushing people to suicide.
Just shows nobody actually needs blockchain even for decentralized systems
There are fundamental problems with distributiveness (which may be reduced to time/timeout handling) which make such task extremely difficult.

Though there were many attempts to do it, I would just mention Erlang and Akka.

The answer to your question is close to the answer for "what's wrong with Akka"
Ask HN: What tech utopia/horror ideas do you see materialising soon?
What i see happening soon is:

With all this recent AI stuff where it is able to create content that feels real
I started to think about how AI could just create the world for you.

Since we already are basically living in the internet we could have
some terrorist organization finding an isolated enough person and attack him with a program
that would generate a bubble just for him: fake friends, fake events happening, fake influencers and news programs just for him, basically whole internet content
and then only reality check would be talking to other people (which Trump us taught is also not necessarily true "fake news" argument)
and then easily this person can be pushed towards some criminal or whatever activity.
If the same thing is said about A and B, it is not guaranteed that A=B, unless that thing specifies equality. Anyway I agree with the article that microservices are basically modules. They extend the domain of modules. They're usually overhyped.
I disagree with this stance. Creating a file and naming it gives it a purpose. It creates a unit of change that tools like git can report on.
It depends a lot on our ability to handle loss of life in the process of exploration.

We can most definitely get people on Mars by 2030. But we need to accept that some or all of them may die in the process. Are we as a civilisation ready for that?

The technology of actually getting someone BACK from Mars is a whole different thing.

In the worst situation we would have the world's most expensive reality survival show, watching when astronauts slowly die of starvation on Mars because hydroponics failed and they didn't bring enough dry rations.
Yes, generally that's what we want -- modularity. I think the article touches upon a key truth, that There is Nothing New Under the Sun -- we always deal with complexity and we always find the same ways of structuring our responses to it.

One thing I've observed in a microservice-heavy shop before was that there was the Preferred Language and the Preferred Best Practices and they were the same or very similar across the multiple teams responsible for different things. It lead to a curious phenomenon, where despite the architectural modularity, the overall SAAS solution built upon these services felt very monolithic. It seemed counter-productive, because it weakened the motivation to keep separation across boundaries.
We'll be waiting for you on the Zig side :>
> "out of spec" means that it is out of specification. It is literally not specified.

That's not what it means at all. Being out of spec means the spec explicitly stating that a request with a body should be reject. If the spec does not state that a request with a body should be rejected then you are not required to reject a request which packs a body.
I can't say I agree with all your "okays", although If you prefix them with "In some cases it's okay", then I understand where you're coming from.

The problem is when it's OK and for how long. If you have a team of people working with a codebase with all those "okays", then they have to be really good developers and know the code inside out. They have to agree when to refactor a business login out instead of adding a hacky "if" condition nested in another hacky "if" condition that depends on another argument and/or state.

I guess what I'm trying to say that if those "okays" are in place, then there's a whole bunch of unwritten rules that come in place.

But I agree that microservices certainly aren't free (I'd say they are crazy expensive) and modules aren't free either. But all those "okays" can end up costing you your codebase also.
Respectfully, rants by niche celebrities are not something we should base our opinions on.

If you're a single dev making a game, by all means, do what you want.

If you work with me in a team, I expect a certain level of quality in the code you write that will get shipped as a part of the project I'm responsible for.

It should be structured, tested, malleable, navigable and understandable.
Because often you don't know what to grep for, or search is too general and returns lots of irrelevant results, or perhaps you're just in process of onboaring on the new project and you want just to browse the code and follow different logical paths back and forth...

and when dealing with the code that's well-organized and grouped into logically named files and dirs, you simply can navigate down the path and when you open a file all related code is there in one place without extra 10k lines of misc. code noise.
I want to disrupt the toaster industry.

For way too long I've been getting inconsistently toasted toast out of my toaster. My idea is to introduce cameras into the toaster that are used to recognize when the perfect amount of toasting has been applied. It is a way better approach than just using a timer. I have a few problems to solve...
I switched from C++ to Java too. Still, every time I type `new MyObject()` without a corresponding `delete` I feel like I got away with some sort of crime ;)
Do anything too long it can become dull and sap life from you. You should wake up feeling invigorated, not drained.

Golden handcuffs enslave us and true freedom is being able to have the confidence to side-step into new adventures.
Good luck on your journey
Well, of course it was, nobody is hiding it - you can see the timer in the pool part and the graph showing seconds in the beginning.
Very nice, simple job posting. FYI: The "Some questions people have ahead" link doesn't work for me, it leads to a notion signup page.