skysight-inc/HackerNews huggingface dataset:
While I'm not disputing the limit numbers or whatever hardship they might cause, it's worth noting that this is a basic limitation of the original Lambda model and maybe FaaS in general. The capability comes from running a giant pseudo-infinite mesh of isolated execution environments that load your code and execute on demand, while having to buffer both the request and response to make sure clients are protected from the details. This buffering means that size of the buffer will always be limited - the team managing might make the buffers bigger based on experience, but it's not a solved problem.

ALB to containers or servers is a different beast - here the entire request and response need not be buffered at all (there might still be a very small buffer, mostly negligible), so streaming responses, websockets etc become possible.

We use lambda to resize images, so we do push against these limits a bit, but it's a fair tradeoff for the advantages - no worries about CPU throttling from too many requests, no waiting for servers to start for spiky loads etc.
Maybe that would not be an issue if HN had markup worth using. Like bulleted lists.
There is, and has been for quite a while an option to change that. Look for reentrant / pure.
No, you can use the reentrant interface, flex can handle that:

https://www.gnu.org/software/bison/manual/html_node/Pure-Cal...
> we still manage to drive

not amazingly well, though, because there are millions of victims each year

SDCs are supposed to be better than us, so more sensors make sense.
Take the gurantee, the whole point of these sorts of things is to cash in on the people who risk choosing number 2.
Wine is a compatibility layer and in fact supports what i was saying in two fronts: first, it is something developers decided to do and second, the Windows application does not need to care about the 1% that uses Linux on desktop and force the cross-platform complexity and bloat on the Windows users, but instead the Linux users (who as you seem to imply do not mind that extra bloat) can use Wine and run the same application on their systems.

Accessibility is something that can be necessary, but certainly not in all situations. Though of all things, it is the one bit that the OS itself can support the most and relieve applications from having to do it themselves (of course this assumes that applications do not try to use the lowest common denominator of OS functionality in order to be cross platform and actually take advantage of the functionality their OS provides).

About the proliferation of devices, this is a great case where what i wrote about leaving things to other applications applies: instead of having a single application try to cater to a bunch of different devices and input methods (and thus providing a mediocre experience on all of them), it is better to have one application tailored for each device and input method.

And note that i'm not writing about what is being done but what about should be done. Of course this is in my head, otherwise i would say that things are actually nice now.
I use docker swarm (mode? I am not sure) in production and it works great.
Deliberately designed to serve as clickbait.
It's not uncommon for new prototype-level technologies to become significantly cheaper when you (i) improve processes and (ii) increase scale.
See Lemon, which generates re-entrant and threadsafe parsers and is used in SQLite:
https://www.hwaci.com/sw/lemon/
Ah, these may not be standard in the developing world but lots of cars have some of these features in the US. Teslas have the ground-bounce radar thing: https://www.youtube.com/watch?v=APnN2mClkmk&feature=youtu.be

Almost every modern car in the US will have the blind-spot warning. My 2018 Subaru does.

There are lots of these. As early as 2018 models of cars you could get features that turn the wheel to keep you in lane, follow the car in front of you at a pace that's safe at a distance you desire, and break in an emergency if the car detects an imminent collision.
Yet another of this submitter's collection of Amazon affiliate links with no added content (tag=mostrecommendedbooks-20).

A single recommendation is enough to make this list. How handy.
Corruption is simply part of the price of operating cost in developing countries, not an impenetrable barrier.
That reminds me of when a new scrum master joined the company and he was setting up meetings as "games". One time he was throwing around a ball and only the person who held the ball was allowed to speak. Everyone was looking at each other like WTF is this... It's clear to me that the scrum master was training us to become docile office cattle; making us receptive to the increasingly rigorous daily prodding and milking at the hands of our corporate masters.

I quit the company not long after.
Everything old is new again. Except now it's on someone else's machine and you have to pay for it...
Agreed. I've been saying for years that if you go with Docker-Compose, or Amazon ECS, or something lower level, you are just going to end up rebuilding a shittier version of Kubernetes.

I think the real alternative is Heroku or running on VMs, but then you do not get service discovery, or a cloud agnostic API for querying running services, or automatic restarts, or rolling updates, or encrypted secrets, or automatic log aggregation, or plug-and-play monitoring, or VM scaling, or an EXCELLENT decoupled solution for deploying my applications ( keel.sh ), or liveness and readiness probes...

But nobody needs those things right?
Lots of shallow dismissals in the comments for this and it seems to be a trend every time microservices come up.

"N Microservices for $BUSINESS_DOMAIN ? Crazy!"

Can't we just taka it on good faith that the engineers who do these blog posts have at least a modicum of competence and therefore their solution has _some_ merit (that is worth discussing) rather than just "Micro-services bad" dismissals?

<sideshow bob>Yes I realise this can also be taken as a shallow dismissal of the shallow dismissals</sideshow bob>
Both flex / bison can deal with reentrancy. Granted this is relatively new as far as flex & bison goes-- the functionality was introduced in mid-2001.
> However, once a feature is ready to be reviewed (and then released), I'm arguing that developers, before submitting their work, should re-organize their commit history: remove WIPs commits, remove refactors that happened during development, squash distinct commits that are part of the same logic, amend commit messages, etc.

I agree that this is the optimal solution but isn't this a hefty piece of work that even might introduce subtle bugs?

Eg. I'm thinking of the overall feature needs work to be done in two separate "areas" of the code base and your wip-commits are touching these two areas "separately". Then when you are finished, reordering and squashing the wip-commits into two atomic commits seem like an obvious thing to do. But in a minority of commits you change that tiny little shared part back and forth, from both contexts. Finally you figure out how the shared part should work in the final wip. When you try to reorder the commits the changes in the shared part changes order with leads to merge conflicts when rebasing/reordering/squashing that needs to be solved.

So I'm on the fence of doing that extra work which in practicality could involve an unknown amount of "made up work" to get the clean atomic commits. And those commits then risk being a lie since the reordering, like the shared part in my contrived example, could have made that the first "atomic commit" that never existed also has a bug that never existed that someone down the line potentially stumbles upon when bisecting.
Docker swarm?
This is an amazing observation for someone unfamiliar with structural typing. It's probably also why python programmers tend to enjoy Go.
> there is a trivial migration path from docker-compose to kubernetes

The migration path of docker-compose to swarm is basically:

eval $(docker-machine env my_cluster)
docker deploy --compose-file docker-compose.yml PROJECT_NAME

I have looked into k8s and it wasn't as easy as this.
Self-driving tech is still at an immature stage while the bar set by public is super high; even human-level self driving might be unacceptable for pervasive adoption. Anyway you can use both Lidar and camera. It's not too late to worry about this cost-performance trade-off after making it actually work.
$300 is more than minimum wage in some countries.
This whole article is very polemic and promotes an ANTLR book. It is futile to comment in detail because nearly every statement is false.
Agreed. I'm resisting the urge to flag it.
Pesky monitoring and logging just makes you notice bugs more and get distracted from making the world a better place
btw. I would never run OpenShift after the CoreOS debacle. This was a really sketchy move and still is.

Yes RH did a lot for k8s, but killing of a working distribution without a direct migration path that is like "start again". will make your customers angry.

also I think the OpenShift terminology is way too much and OpenShift should be a way more thinner layer on top of k8s.
First response is often generated by automat. A generic one “hello this is X ill take care of your case” and the next real person response can happen the very next day when the ticket urgency is CRITICAL. Thats hilarious.

The best support I got a mispleasure to work with didn’t even know how the service Im having an issue is even working... And it was a “technical” ticket.

Seems like after the last round of pouching of best support engineers by AWS, Azure is left with only outsourced mob.
Show HN: Tubda – An easy way to play our songs and videos together with friends
I get the same feeling from cheap hotel art. Dull colors, fairly abstract, and feeling kind of "soulless"(?)
Surprisingly, it is possible to build a profitable business in this space. I looked them up and they're (very slightly) profitable. They also operate in multiple countries, which likely adds complication to their infrastructure, so it's not as ridiculous as it sounds.
This is the Monty Hall Problem, and though counter-intuitive, is well understood: https://en.wikipedia.org/wiki/Monty_Hall_problem
I find it interesting that many people don't seem to know the "git rerere" option [1], even experienced devs. With long lived feature branches that takes away 95% of the frustration people have with rebasing.

Theoretically, one could also use merges on the feature branch and rebase once at the end of development (as git will auto-remove all merge commits during rebase), but that only works well if you have just a single commit between merges on the feature branch.

[1] https://git-scm.com/book/en/v2/Git-Tools-Rerere
I don't want to argue about the general idea but a lot of the things in your timeline don't really match with history:

* The desktop metaphor with its files was not popular, and not successful on 8-bit machines. It was technically possible to get something with a desktop metaphor running on these machines, with enough clever trickery -- e.g. GEOS ran on the C64 and the Apple II. But it wasn't very useful, because they also lacked the storage to make it useful. Things like GEOS or GS/OS had their users but these things weren't too successful in the realm of 8-bit machines. In fact, many of them didn't even show up on 8-bit machines until way into the "16-bit era", when 8-bit computer users began to covet windows, buttons and icons.

* By the time the iPhone showed up, in 2007, skeumomorphism had been the way to design interfaces for at least 8-10 years. See e.g. Kai's Power Tools, which in the mid-90s looked like this: https://alchetron.com/cdn/kais-power-tools-5461d370-1529-47a... . KPT was, admittedly, an outlier, in that it was more whimsical than average -- but Aqua/OS X interfaces and, later, the iPhone's interface was not fundamentally different from the status quo, they just looked better. In fact, the iPhone came up late enough that, when it did, its interface was seen as a "final word" on the matter because the field was already extremely mature -- the time for experiments was long gone. The iPhone didn't spark a new fashion in UI design, it adopted what was already the fashion in UI design, everywhere.

* Fast-loading and flat are completely orthogonal. Today's websites load way slower than the websites of the Geocities age.

* Early Windows version were very much colourful and whimsical because of the VGA palette. By the time Microsoft could bet on enough users having 256-color screens (in the 3.1 age), two major Windows version had passed. The default background in Windows 2.0 was a retina-piercing cyan.

* Early Macs models were certainly not whimsical in terms of colours, but that had nothing to do with fashion -- it was because they were monochrome.

* Most 8-bit machines certainly used very vivid colours. Most of them could (and most users did) use a TV for a monitor, and the palette choice was deliberately picked with this in mind. The first Amiga Workbench version had an eye-stabbing palette, chosen so that things could be read even on poor quality, black-and-white TVs.
No it is not and never was. Sales people - going back a very long time and include fully traveling ones - are not employees? How about traveling service technicians, not infrequently located all over the country, far from any company office? Home office - not uncommonly full time even, e.g. the company I work for does not even have an office but people employed all over this and other countries - are not employees? Please don't arbitrarily redefine "employment" to make your point.
My friend and his girlfriend discovered that they unconsciously do listen to similar songs at bedtime. Oh, how beautiful would it be to help them actually play the same songs at bedtime, sharing that vibe, that deep emotional state in real-time, I fantasized.

Months later, I and a friend across the world got bored while on a long video chat. She decided to play us some songs to keep the vibe. Bummer! We realized there was no easy way to share such a vibe, that emotional atmosphere. Then I decided to fix this.

Tubda is not just an app, it's an experience.

Please kindly give it a try with your friends/teammates and tell me how y'all like it.
Simply Explain What Bitcoin Is to Baby Boomers in 3 Steps
At my current job when I started people were doing git flow. It was horrendously complicated. I got rid of it and now everyone is happier.

The idea is really simple. You have one eternal branch, "master", which is your integration branch. This is set to be the upstream of all other branches during development. That means it's really easy to keep rebasing on master every day. When your branch is ready it's merged into master (I do fast-forward only, but that doesn't matter). When you want to release, just tag a commit on master. If you want to maintain releases, make release branches for these and cherry pick fixes from master. Reset the maintenance branches to whatever release you are maintaining. It's easy.
Part of the justification of the high court is that Uber disables accounts of drivers who refuses courses.
Uber also hides the destination.
There's not much room for a choice.
People are definitely looking at history when running git blame on a file. We want to know exactly who, when and why a change was made.

Squashing down a PR to a single commit erases all of that history and we have no idea when the change was made, who made it, who to talk to, or why it was made other than it was part of a larger feature set.

It might work fine for smaller PRs, but where I am we have multiple teams each working on a task that can take months to complete with lots of testing before it's ready to merge into a release branch.
our Great Moons and our Great Stock Market will never fall!
Two virtual machines are more than enough to a startup for the first 2 to 4 years.
Same with horses
Because FOMO increases engagement, which means bigger ad sales: the user has to keep coming back or they miss the ephemeral content, same reason F2P-style games have daily activities.
Unfortunately, this kind of disclaimer is something you eventually acquire as a general habit.
I'm suspicious of 3X3 = 9 and 1 - 1/9 = 0.88888
Prosecutors, even high profile/positioned ones, have a finite amount of resources. At the end of the day it might be romantic to go after a megacorp but a prosecutor's job is to persue justice against criminals, you might get a few high profile executive types and justice for one family (if you're the type to consider beyond the defendant) but with those same resources and time you could probably lock up at least twenty violent, in the real way, deadbeats. I'm not saying that's the way it should be, but I think it's worth acknowledging because it's why the problem is hard to solve. Everyone wants to see big fish getting hard time, but reality looks more like Harvey Dent's speech to Commissioner Gordon and that's for the good prosecutors.
I was chatting with a B&N store clerk the other week who hinted at this plan. Great to see it become official.

Their new “indie” approach sounds intriguing and akin to what Amazon Books tries to accomplish. In today’s world, the physical store can no longer compete with the web’s infinite selection, but can still offer value in curation and presentation.

Don’t know if B&N will pull it off but wish them the best. I love bookstores and would hate to see them die.
There are higher cross-border fees in the U.S. too. I don't know how this compares to the competition.
That’s a different issue. This is not just using structural interfaces but downcasting to even lower interfaces without warning. That is, the method lies about what it’s looking for.
Bash Argument Parsing and Quoting (2016)
I will in the future on my CV also have a "Will Not Work With Skillz-Matrix" Kubernetes goes on first... Unless I'm applying to Google or something of similar size.
The difference between a court and a contract like that is that the court is impartial and has a clear bar of criminality ("innocent until proven guilty" to some standard of proof), whereas it's always in the company's interest to fire you at a mere accusation of a potential crime (or non-criminal wrongdoing)...
The parent conflates copyrights with trademarks.
There are a lot of people here very confidently stating that LIDAR isn't necessary but seemingly forgetting to link to any actual evidence of fully autonomous vehicles that work without it. The issue is that human vision isn't just vision, it's vision linked with a ridiculous general intelligence that we're no where close to reproducing. So humans are great at categorising the objects they see, and reasoning and how they'll behave, which is why we don't generally need LIDAR.

So it's just as much about how humans can reason from sight as it is about how good their sight actually is. It's very possible that by the time you've built a computer capable of the same sort of reasoning that humans do, you've actually solved, well, artifical general intelligence and you're no longer designing a car at all - because the AGI took that job ages ago.
Here the explanation and the picture describes the best strategy https://en.wikipedia.org/wiki/Quantum_pseudo-telepathy#The_M...
"Pod, Deployment, Job, CronJob, Service, Ingress, ConfigMap, Secre"

Wow as a new developer coming onboard your company, I will walk out the door after seeing that, and the fact that you admit its a small serivce.
Ethics Explained to Designers
If he did say anything like that I'd agree with you but this is most likely distorted through retelling.
> ANTLR uses an algorithm [...] called ALL.

Why is the tool called ANTLR if it uses an LL algorithm? Did earlier versions use LR, or is it just a confusing name?
A church? If that isn't a crooked move, I don't know what is. Kind of fits the picture, so.
Git blame is very useful, yes. But what do you need to know? Do you need to know that Josh made a commit called "fixes" at 3pm on a Wednesday (while it was raining), or do you want to know what feature this commit was part of?

I don't argue for squashing down the whole branch into one commit. That's silly and could be throwing away valuable information. But cleaning up the history using rebasing is still possible. We use "fixup!" commits so that a simple autosquash does the right thing most of the time.

I've actually had developers undo over-eager squashing before and introduced them to both the reflog and interactive rebasing. They are shocked the first time they learn to "undo" a rebase, but it's a liberating experience to actually understand git.
Minecraft to Metasploit. Game hacking could start your cyber security career
Where is the Supercomputer for modeling the global spread of pandemic disease? When was it built? What are its specefications? Who operates it?
funny thing about git flow is that working with nvie (who coined/created it) at gitprime, they did NOT like it in practice. we just used feature branches go figure
Shouldn't that be an unconditional ban of all associated accounts
It's been a while, but I had some fun using the "lemon" parser generator[1] used by SQLite. Worked alright for something where regexes weren't enough and I couldn't be bothered to write a custom parser. Probably has the same cons that lex/yacc would get, according to the post.

I do have the ANTLR book, but to be honest, if I would have the task of doing something more involved and where integration isn't as important (i.e. it could be an isolated command, not a module for huge Java/C# app), I'd probably be more inclined to get deeper into SML/Ocaml than ANTLR for this.

[1]: https://www.hwaci.com/sw/lemon/
I'd be in favor of a piece of regulation that requires the extension declare its scope of behavior (e.g. "no analytics", or "no data exfiltration"), and then any automatic update that breaks this declaration means the developer is subject to fines and/or imprisonment.

Most of the extension problems boil down to either a) malicious developers, and b) developers of popular extensions which take money to include malicious functionality, or sell the extension to a third party.
There are 17 lines of text output to verify the installation choices, of them 5 are devoted to opting out of the anonymous telemetry. The wording seems clear.

NOTE:
Anonymous usage stats will be collected and sent to Google Analytics.
To opt-out, pass --disable-telemetry option to the installer or export
the enviornment variable DO_NOT_TRACK to a non-zero or non-empty value
(e.g: export DO_NOT_TRACK=1).
Why the Shop Safe Act is a mistake, and how to fix it
I couldn't agree more with you. Too often we expect the same outcome when throwing people into a new environment, and without clear processes, expectations...
Bain – The Battery Indicator
林檎 is one way to write "apple" in Japanese using kanji, although it's usually written in kana as リンゴ instead. https://jisho.org/search/%E6%9E%97%E6%AA%8E

It's called 偽中国語 for a reason: Japanese speakers may know some obscure kanji for a word, but that doesn't mean they're the same as the hanzi a Mandarin speaker would use.
Is it not the case that most serious parser implementations are hand-written? In part because it makes it so much easier to provide good diagnostic messages. I feel like every other project moves from parser-generators to hand-rolled parsers and levels.
It wasn't disclosed on whether stolen IP was used - Uber had (still have?) to cooperate with Waymo, inspecting their hardware and software stack.

The pedestrian ultimately got hit because a lot of fallback systems failed: They disabled the software's ability to emergency-break (1), they disabled the cars' systems to emergency break, and the operator of the vehicle was distracted, not reacting in time.

(1) This was actually done due to false-positives, i.e. the car slamming on the breaks in non-emergency cases. (I find that's a relevant point, because without that detail it just sounds more ludicrous than it already is).
The Life, Career and Tragic Death of Pop Smoke