skysight-inc/HackerNews huggingface dataset:
Federal prosecutors are all appointed, not elected.

Your point stands. Napoleon once said "the most powerful man in France is the juge d'instruction", the prosecuting judge (a peculiar French institution comparable to a prosecutor).

Given how much Swartz achieved in his brutally short life, we can only imagine what we've lost with his passing.
I can't use current Reddit without Reddit Enhancement Suite - https://redditenhancementsuite.com/
More and more I think of OOP and services as the same thing at different scales. Objects are services, dependency injection is your service discovery/orchestration layer. Your monolith is already a microservice architecture.

In the end, extracting a microservice from a monolith built this way is just a matter of moving the implementation of the object to a separate application, and making the object a frontend for talking to that application.

The single biggest reason OOP gets a bad reputation is because lots of languages insist on treating OOP as the be-all end-all of code structure (Java and Ruby are particularly bad examples) and insist on trying to shoehorn this sort of logic into tiny dumb pieces of pure data.
I'd sum up with: simplicity is your friend...

recently I am getting more and more thoughtful about "accidental" complexity we add to our solutions in form of dependencies on external libs/module, frameworks such as IoC, log services anyone ;) and on the architectural side microservices etc.
How about Lisbon to New York?

https://en.wikipedia.org/wiki/Bering_Strait_crossing
That open source experience was what led me to this new life philosophy.
The conclusion is to use an appropriate classifier. https://en.wikipedia.org/wiki/Sensitivity_and_specificity even gives an analogous example:

> Suppose a 'bogus' test kit is designed to always give a positive reading. When used on diseased patients, all patients test positive, giving the test 100% sensitivity. However, sensitivity does not take into account false positives. The bogus test also returns positive on all healthy patients, giving it a false positive rate of 100%, rendering it useless for detecting or "ruling in" the disease.
Lichess is libre, ad-free, gratis, open source, doesnt require a login, or anything. Chess.com cant even compete for me.
The best migration is no-migration. That is not having to move data at all. This becomes increasingly more important with larger datasets. One way of doing that is to simply serialize data in something like Protobuf and have a generic schema that rarely/never needs to be altered[1]. Adding a new field to the Protobuf is a no-op.

[1] https://kevin.burke.dev/kevin/reddits-database-has-two-table...
Yeah. I don't know the specific percentage, but I'd guess the vast vast majority of Azure code is C#.

Source: I'm a former Azure intern
While it sounds painful because of the inefficient development & testing process, I think that if that day is spent on research instead (looking for a better solution or reading existing code) it is OK to spend 1 day on 3 lines of code.
Perhaps we should put computers inside each businesses location, to minimize the blast radius of any specific outage and make people take responsibility for their own stack.
Ok no argument from me there :)

Maintenance and the automation of repetitive tasks are in my view part of DevOps, but not every dev in a team has to participate at the same degree...
> It's important to get the idea out there that human lifespan can be extended, so more funding can be directed to that.

The jump from "could" to "should" seems questionable at best. What's so great about the rich elite living to be 200 years old? Would you like a bunch of people from the 19th century still around, influencing politicians with their money today? It would slow down the rate of social progress. It would also increase wealth inequality, since money hoarded by one generation tends to be squandered by the subsequent. There's also an argument to be made that science advances one funeral at a time; keeping people around loong after their expiration date would likely slow down the rate of scientific progress as well.
i.reddit.com works pretty well for phone browsers, quite minimalist and mostly not broken.
I feel like this makes it even more confusing as to why this "drop-in replacement" is yet another new competing project rather than an upgrade/enhancement to an existing linker (such as lld)... has open source as a community concept failed so hard that people are unable to even contribute to and collectively improve projects they themselves started?
Interesting. I was thinking that you pay more attention with manual. The point of manual shifting is not in how the car works. The point is in knowing what will happen before it will happen.
Depends on the service are

I have some services which can cope with a 98.5% downtime, as long as they are available the specific 1.5% of the time we need them to run, as such "the cloud" is useless for that service
Come to Florida. We are actively hiring. If Google does not want you, we do! jobs@bytefederal.com
How does this work? Is it a C++ lib with python interface? Does it use llvm for the JIT? ...
Turn 2 and 3 on their side and they become our version.
I'll give one counterpoint:

When did you see anyone on TV mention Digg?

Reddit's become mainstream, it's quoted by serious news outlets, joked around on Last Week Tonight (and other politic joke shows), and I'd say it's as likely to disappear as Facebook. Which is to say, surely but very slowly.
Is there a word for the phenomenon "company does something morally questionable to increase (short-term) profits"? I feel like it happens all the time but society just kind of complains and then forgets about it. If we have a word for it we can call it out and keep track of it better.
Nice, but I'm afraid real world CSVs are a lot more complicated than described so don't use this code in production.
NYU Students, Staff Must Get Covid Booster Shot to Be on Campus Next Semester
The writer also demonstrates that even for something like "sapphic boob anime", professionals make a lots of mistakes. That would imply that the level of Japanese and English needed to translate properly the works of Japan's literary greats is way higher than that.
I don't want to write an asking price here, and honestly I don't know how to valuate an open-source project. But I could have been working for Google as a staff engineer and enjoy a decent salary instead of doing this project, so, well...
You still need to turn it into real money at the end of the day.
Those boards have better moderation, something you need regardless of AI, which is my point.

AI doesn't add more danger to the situation, you just need to moderate as usual. If you are using some computer program to add more content to your web site, you will just have more content to moderate. News aggregators do have this problem for example, as sometimes automated crawlers post sensitive content and that needs to be marked & deleted before being published.

Saying, "oh but our algorithm can cause depression, so we moderate the access to it" doesn't make sense, as any content can cause it and needs to be moderated.

That's why content moderation is one of the hardest problems of this age.

You use computers to do it? Computers develop biases. Humans? Same! It's very hard to scale and is a problem only remotely related to AI-generated content because AI generating content increases the input to your moderation system.

Now I hope it is clear what I'm trying to say :)
For 1 and 2 you can go straight to the sources:

Volume 3 of the Intel 64 and IA-32 Architectures Software Developer’s Manuals, Chapter 22: Introduction to Virtual Machine Extensions:

https://www.intel.com/content/www/us/en/develop/download/int...

Volume 2 of the AMD64 Architecture Programmer's Manual, Chapter 15: Secure Virtual Machine:

https://www.amd.com/system/files/TechDocs/24593.pdf
The image library also runs sandboxed, and they found a way to "escape it with ease."

Sandboxes don't reduce the need in having programmers with straight hands. They just trade less safe APIs, for ones deemed more so. You will have as much holes in the sandbox, as much APIs you add to it.
"rubberhose him just to be sure"
In some languages, you can enforce boundaries within a monolith nicely using the build system. The key is to break the build up into a hierarchically structured set of libraries somehow where each library only gets to use those libraries it is allowed to depend on architecturally. Independent bits of business logic would need to go into libraries that cannot "see" each other when they are compiled. Everything would still be part of a single build process and still be linked together into a single big program at the end.

The exact method depends on the language. In C/C++, you'd limit the include paths for each library. In C#, you'd have to compile different assemblies. And so on.
Yes, services should definitely encapsulate their state layer.
yes and no. i totally get what you are saying but this problem has been solved lately in my opinion.

Also deployment is part of code organistaion no? i like to point out the fact that i explicitly mentioned you do not need to decide, you can use both at the same time but i would like to try to answer your point anyway:

Maybe I am just spoiled with go and github, but those deployment pipelines can be directly integrated into your repository. The same way I can counter argue that your build ci and deployment phase will take significantly more time too and if you change a variable from uppercase to lowercase you will wait for minutes too.

I come from a c# background a long time ago and this has been true with it for eons:
https://xkcd.com/303/

Another thing that I have noticed is that its easily scriptable too. What I end up doing is to provide a makefile into my repository too. This way i can define the build process amongst other things eaisly.

In the end: We have a predefined spec that will create the desired state on a host of our chosing.

Ansible really does not care if you deploy 1 or 1000 "services" for instance!
Tools Like ArgoCD will also deploy stuff when you commit to your master.

There is tooling for everyone available, but what happnes quite often is that the people in charge of the company expected the developers to be all knowing entities that need to define everything end to end. The Kubernetes Space is vast because we are still defining and communication its future.

But recently? I am trying to think of something that would not be completly automateable in 2021
>but removing features takes courage and is actually a form of sincerity

That is false, say I remove the feature X because reason A but I tell everyone that is for reason B. So I had the courage to remove X but I did not the courage to be sincere, maybe I am not sincere with myself and the real reason A is that the code was written by somebody else in the past and I want to implement new cool shit and not read somebody else code, but I can't admit that I don't care about feedback because I might be replaced as a project leader so I invent bullshit excuses like blame the previous developers that wrote bad code, blame the user that are using it wrong or invent some bullshit UX story with no real user tests to push my egotistic vision on everyone else because I am really an Apple fan but I could only get a job to work for RedHat
Never had issues moving codes out of Google authenticator and I've changed like 3 phones since I use it.

There's an easy way to transfer/import the codes over.

Maybe the thing is that authentication procedures should be tested to not get surprised when something doesn't work anymore
> One or more (relational) databases, depending on whether you’re gonna go with single database per service or not

This imho is where serious complications can come in. A single database for all services is a good trade off if you want the nice parts of microservice decoupling but not the headaches of a distributed system. Just perhaps don’t call it “microservices” to avoid having to deal with arguments from purists who want to explain why this is not true microservices, etc.
All ideas that are good in principle, become absurd the moment they are elevated to a kind of dogma, applied to every problem, no matter if it makes sense to do so or no.

Microservices are no exception from that rule, and often repeat the same mistake as OOP did with its promise of "reusable code".

Does it sometimes make sense to break some larger services up in smaller ones? Yes.

Does it make sense to "factor out" every minor thing of the implementation into something that can individually be manhandled into a docker container because at some point in the far future, someone may save a few minutes of typing by talking to that service? No.

Why not? Because on the 1:1000 chance that what the service does is actually exactly what that other thing requires, it will probably take more time to implement an interface than it would to simply implement a clone of the functionality.
I still do. Of course dabbling into REPL-based solutions in my youth might have influenced that.

For me it is crucial to always have have the code in some compile-able and testable state. I iteratively work towards the simplest, most naive solution that gets the job done. After that it is refactoring time and I form it into a proper solution.

The reason I do so is because only after having coded the naive solution, I have an concrete and proven correct understanding of the task and can pick the appropriate abstractions. I always see colleagues with an less iterative style use premature-abstractions and over engineering on the basis of "we might need it" instead of knowing.

I do invest some time into thinking about the right data structure though. (Not much about algorithms, as they mostly follow from the data structures anyway.) Also if I code a well understood problem, I might use a more top down approach.

(Not a critique of your workflow, just wanted to share mine.)
While we're on the subject, floating cloud cities are a potential method of colonizing Venus (the dense atmosphere means buoyancy is more powerful). Brings a new meaning to "on the cloud".

https://en.wikipedia.org/wiki/Colonization_of_Venus
See, I specifically remember Debian maintaners arguing that they "don't need HTTPS" on the default repos because it's signed anyway. Now it has backfired on them. (Of course, the better solution is not blindly trusting every GPG key for every source. But if all of the users' sources had HTTPS, that would have mitigated the issue.)
I'm not arguing against unit tests. Just that using them to speed up iteration is not a good way to approach that problem. They can of course be useful for other things. And obviously the things they don't test will still be found by the client in particular all the things you miss by not actually increasing iteration speed.
somebody will still have to store and serve the blockchain, right? So same problems...
> Signal drastically recompresses any image sent. The only end to end encrypted software I know of that allows that is iMessage.

I believe they wont use Signal's own client to send their exploit. Client side TX restrictions make no sense.
WSL 2 GPU Support for Docker Desktop on Nvidia GPUs
> I vaguely recall someone telling me that the qemu source code is fairly readable [...]

That someone was either pranking you or knows a mysterious part of the qemu codebase that's unlike the rest of the criminally underdocumented qemu soup. Or my standards are too high.
That's right, downvote my user experience why don't you.
I find with microservices, they are a fake separation of concerns. When I have to work on something, and it covers two or three services, I'm actually working on a mono app.
I've found smaller "service" classes that do one job meet the same need. One or two public methods "perform" and "valid" seem to work perfectly.
Thinking about it, since it will be running under Windows, maybe this would be a nice touch:

[6] https://ollydbg.de/Jason/index.htm
The Effort to Track Killer Asteroids and Comets
> What if the product (department) doesn’t give a damn about the underlying system architecture? I mean shall they?

They should not. Either it works correctly, or it doesn't. Even buildings need to be useful, even though people might admire the architecture. No non-technical person will admire your microservice or whatever architecture.
And mastercard doesn't require them to get a photo id of their users.
If there’s no organizational barrier (e.g. microservices architecture, separate repos with strict permissions) that will prevent devs from leaking abstractions across technical boundaries, those well-defined modules and interfaces will devolve into a big ball of mud.

I say this with the assumption that the team is large and members regularly come and go.
In other news: If I can intercept the log messages (unencrypted remote syslog, or log file public accessible, log messages also shown to the user) I can still just inject stuff like "${env:DATABASE_PASSWORD:-xxx}". Lots of people are only focusing on the aspect how this can be abused to inject arbitrary code, while it is actually a similar class like SQL injections: Blindly trusting user input instead of doing proper sanitization.

(The whole discussion why a logging mechanism should support the whole JDNI stuff is still perfectly valid).
You can frame anything being "a tool". But if you want to stay within your logic, then this is a very specific "tool", it is supposed to directly interact with people, not machine to machine, and as such it can have consequences which are unpredictable. And no, human to human interaction is mostly NOT unpredictable, we act according to social norms and have common sense, otherwise you're not a proper human.

This is not a new issue but is heavily researched in the certifiable AI area.
If you just turning million knobs randomly based on an architecture and the biased data you have, of course you don't really known what you are doing.
I personally feel like the contrast is fine, but the light mode does fail the lighthouse contrast accessibility check, so you may have a point there.

I disagree with your other complaints though. Buttons are pretty obvious based on context clues and placement, as are highlights. Text fields also rely on context to communicate their function and furthermore more, they are labeled. As is the colour picker…

I’m curious to see examples of an inline color picker you like, as well as how you generally expect forms to be styled. I looked for a few minutes through some UI libraries I like and basically all of them handle the color picker the same way.
Probably the fencing. We have enough pseudo-experiments now that we can say the fencing makes a difference. There's a carpark in the UK that had trouble adding fencing, so they closed the top level.
Analysis of 88K matches shows soccer outcomes becoming increasingly predictable
Microservices is kind of a superpower that allows you to choose where you want your complexity to be. You are supposed to start with something simple, so the microservices decision needs to come in later.

Not starting full in with microservices is a good pattern.
Being a student can be especially depressing, odds are that people will get better once they have that phase behind them.
Antennas can be hidden - they’re phased array and not aimed. Packets will be routed between satellites so nearby ground stations will not be needed

Starlink transforms the internet more than people realize
sci-hub doesn't need it; just look up the latest URL on wikipedia.
It was a great article, thank you for this sentence
Are you sure your time is really best spent coding? Just because you are able to do it doesn’t mean it’s the best thing for your subordinates or company.
When microservices were new they brought a whole slew of new technologies and architecture patterns with them: SPAs, JWT authentication, micro frameworks, REST/Graphql, containerization. Things that solved problems people were having with the previous monolithic approach, all above the lack of maintainability and composability. So I see the term microservice today not as something that's measured in lines of code, but above all by embracing the new technology landscape that came from it.
2021 Reflection Exercise for Founders
There's a lot of praise for Rails. Reading the docs and watching the demo I understand why.

But what are its problems? Where will I hit a barrier?
That's correct. I'm the author of Reveddit. A few things like user pages and the desktop extension work entirely without Pushshift. Threads can function somewhat without it. I maintain a FAQ with details of how it works in case anyone's interested,

https://www.reveddit.com/about/faq/
>nice parts of microservice decoupling

If you require microservices to enforce decoupling you're "doing it rong"
The situation you describe is arguably different, if you eval() code you just fetched from an HTTP server you are deliberately, knowingly doing something very dangerous and it's only your fault. You are the one loading and cocking the gun.

By the way, you can do the same thing everywhere, nothing stops you from doing

system("sh -c \"wget -O - someurl | gcc -x c - && ./a.out\"")

in C and allow the world to pwn you. What is arguable here is that in this case it is definitely not the language or the system's fault if their users are so dumb to invent a creative way to abuse a facility intended for a different use.

Viceversa, the JRE includes and standardizes facilities to potentially download and execute code without any reasonable sandboxing by default, out of the box, in the standard install. It's as if Python had mandated by standard to check if the data passed to `eval()` is an HTTP URL in order to download and eval() whatever resides at that address. It's not the same by any margin. One thing is to shoot yourself in the foot by mistake , one other is to have in your toolbox a device that by design chops your feet off. The thing that bewilders me is that the whole "let's download untrusted .class files from the Internet" thing was a deliberate design choice and it took people 25 years to realize how idiotic it was. There's a whole sea of difference between that and what you've described.
Show HN: A framework for building Markdown extensions
Service oriented architecture then...
I have been skeptical that antibodies are a good proxy for vaccine effectiveness. Your immune system "remembers" how to create antibodies, and there's no clear reason why it would continue to produce them after an infection has been eradicated. So I would expect antibody levels to always drop off naturally over time until your next exposure (or vaccine) with little or no impact on actual effectiveness, regardless of the virus or vaccine.

I mean, I suppose that also suggests that "high antibody loads" indicate your immune system is an a high-alert state against coronavirus, actively fighting the virus (or what it thinks is the virus, the vaccine) and a "low" load a less alert state, so perhaps the rapid immune response in a "high alert" state is better...but surely there is some reason our immune system doesn't remain in a high-alert state indefinitely?

[Edit - plus, of course, antibodies are far from the only immune response, they're just the easiest to measure, something that also makes me very leery of their use as a metric.]
Maybe alternate each computing layer with a cooling layer made from gold (with holes for wires obviously).
It'd be extremely difficult to make a crossing of the bering strait work practically.

It's not just the technical challenges of building a bridge or a tunnel in pretty harsh conditions. It's also that on the russian side there is a huge area that has almost no human settlements and no infrastructure. You'd have to build a train line through an area of nothing. That also means it's difficult to imagine intermediate steps (e.g. first building half the rail line to even get there).
Just write it in Rails, if you ever reach Rails limits, it means you've made it :-)