skysight-inc/HackerNews huggingface dataset:
This is neat but totally leads to false "validation". This is slightly better than just getting an email. Product Market fit (or even Problem Market fit) is more than someone just imagining their future best self as being interested.

True validation has the prospect part with something of value, real value, not just an email.

Like, give me $100 and I'll tell you how I've boot strapped a company now worth $4MM. Or I'll tell you how my previous company took $50k investment and grew to be worth $60MM.

Only folks really interested in the problem space would part with something of value today for a solution tomorrow.
We used to have to acquire large numbers of quarters to do our laundry in the USA, and the easiest way was to feed a $5 bill into a vending machine and press the 'reject' button. Clunk clunk clunk clunk...
Or existing in the first place. Or being fundamentally possible to implement in the first place (I say, glaring at boto3).
White House Is Not Contact Tracing ‘Super-Spreader’ Trump Rose Garden Event
> FB used to also websocket portscan your localhost + LAN on login from a fbsbx.com domain that also attempted to load native code/windows media player playlists/SWF/Java/Shockwave

That's straight up malware behavior.
From the 50 page report linked in the post, I have the impression that the constraints and features that they want eliminate most of the advantages of a digital euro.

The biggest advantage in my mind would be the elimination of counterparty risk, because the ECB can't go broke. But then they don't want to see bank runs where people convert all their commercial bank deposits into digital Euro, so they'll put a limit on the amount you can hold. So this can't really be used as a safer alternative for bank deposits at scale.

Another advantage I expected would be the elimination of the need for settlement for digital euro transactions. But then they talk about a system of intermediaries who manage the system and who would still have some form of settlement between them?

There would also be a system of onboarding much like for a regular bank account (not anonymous), restrictions on foreigners to limit use as an investment vehicle etc.
I think the actual issue with TLS is that compilers will happily hoist TLS address computations across function calls. It they didn't do that, TLS would be much safer (at least as safe as with stackless coroutines). TLS Address computation is pretty much free in non-PIE code on x86-64 linux so normally GCC doesn't do it, but on shared libraries or on other architectures, you can randomly get corruptions.

I do not think that FLS (at least by default) is the right solution as it would consume a lot of memory, increase the switch overhead and add complexity for little benefit.
> It's very unlikely any such system would face these limitations and would silently ignore data the same way Excel did.

I’ve seen plenty of production systems that ignore or hide errors. Sometimes they’re still logging them, but it just goes to some log store or file that the team doesn’t check until their customers or support team inform them that it’s broken.

Good practice? No. But there are plenty of ways to mess up a non-Excel system and get something that works worse.
Economics includes opportunity cost, so yes, in competitive markets profits will drop to 0.
I remember when they used to sell a physical search box that you could plug into your server.
The same can be done with lstrip("prefix") and rstrip("suffit") for most use cases.
But it doesn't have anything to do with pointers....
I've really never understood this obsession with "preserving" history. When I work on a feature or bug I tend to commit often, because it's cheap, and it can save my ass if I go in a bad direction and break something that used to work in one of my previous commits. I subscribe to a code fast philosophy, and work quickly to explore the space, find unknowns, get a working solution, write tests, and do final cleanup, docs, and optimize if needed. As such this would be a common commit history for me that would end up in a small PR. A large PR for me might have 50+ commits.

- initial prototype of feature x, mostly working

- feature x working as intended in requirements

- fixed edge cases not originally identified when thinking
about feature x

- rearchitect feature x a bit now that it's better understood

- write tests for feature x, most pass

- get all feature x unit tests pass

- a few more test cases for feature x

- and a couple of integration tests for feature x

- code cleanup for feature x

- fix typo from last code cleanup resulting in bug

- better docs for feature x

- fix typos in feature x docs

- update main readme to include notes about feature x

Can anyone explain to me the value in preserving this history, because I'm just not seeing it, and it would completely muddy up the overall git history. There's tons of intermediate work we're not concerned about preserving, like the notes I scribble on paper, so why are we so concerned about preserving all these commits? I admit there's a small chance it's useful in rare circumstances, but I'd rather optimize for the common scenario.
I'm also one of the core developers of Orleans. Ironically, I recently joined Temporal. There are definitely some similarities, but also major differences between the models, especially when it comes to the execution model and fault tolerance.
Nicotine is also an acetylcholinergic stimulant, meaning it aids in the quickness of thought [0]. By removing this from your stack you probably depressed your acetylcholine for a while, making you less able to think clearly.

It might also be the lack of breaks too, but who knows.

[0]: https://doi.org/10.1093/ntr/nty134
From what I've understood it's already rolling out in small steps.
Finetuning a GPT-2 model on logs from a chatting server like IRC or Discord you're active in, then writing a bot to generate messages from a prompt using the model.
Thanks, likewise :)
Finding an alternative to the social part of college is the real challenge. The transferring of knowledge is already commoditized and available freely online.
Supposing you could adapt the ROM/EFI/SMC to work with the new motherboard. (I'm not claiming practicality here, just possibility), perhaps desoldering & resoldering the respective chips onto a new daughterboard or even a PCI card.

Does that make it a Mac still? You could literally replace almost every component in a Mac except for the motherboard and have it still be a Mac, but shouldn't the converse be true as well? If I used the original case, hard drive/SSD, video card, keyboard & mouse, even the CPU, but replaced just the logic board (swapping the ROM/EFI/SMC somehow), it seems to me it would still be considered a Mac. Particularly if in the process the original logic board was rendered inoperative to head off any claims of duplicate license use.
>That said: 40$ per pound coffee is expensive, but buying a 1000$ coffee maker, and searching for a deal on one so you can afford it is no less absurd to us Tea drinkers.

Just to clarify. I pay $6.99/lb for coffee, and I didn't even seriously consider purchasing a $1000 coffee grinder (not maker).

Doing so would absolutely be absurd. I'm going to assume that either I wasn't clear in my comment or you aren't a native English speaker. Either way, apologies for any confusion.
We took Show HN out of the title because the project author appears to be someone else. Show HN is for sharing your own work: https://news.ycombinator.com/showhn.html.

If you're storax and I got that wrong, please let us know at hn@ycombinator.com and we'll put it back.
Cisco ordered to pay US$1.9B in US patent lawsuit, has pledged appeal
> I think you're overstating [...] the paper's impact

Krugman [0] called it "surely the most influential economic analysis of recent years" and adds that it "quickly achieved almost sacred status among self-proclaimed guardians of fiscal responsibility; their tipping-point claim was treated not as a disputed hypothesis but as unquestioned fact."

However, indeed, he cautions that "the Reinhart-Rogoff fiasco needs to be seen in the broader context of austerity mania: the obviously intense desire of policy makers, politicians and pundits across the Western world to turn their backs on the unemployed and instead use the economic crisis as an excuse to slash social programs.
What the Reinhart-Rogoff affair shows is the extent to which austerity has been sold on false pretenses."

I'd say the paper made it certainly easier for the Very Serious People[1] to push through their austerity agenda.

[0] https://www.nytimes.com/2013/04/19/opinion/krugman-the-excel...

[1] Krugman's derogatory term for duplicitous policy wonks (like Paul Ryan) that pretend to be thoughtful and serious and concerned about the nefarious long term effects of debt when discussing stimulus and spending and social programs, but then typically turn around and implement huge tax cuts without second thoughts...
Klondike Big Inch Land Promotion
A very large number of people in the US have access to no public transit whatsoever - and as for sharing a car... that’s what they’re likely doing with their partner. One person uses it to go to work while the other is at home, probably caring for their children.
This is the reason why I want to support such a query for my GraphQL server:

My goal is to allow users of my WordPress plugin (i.e. not just coders, but also non-techies, such as bloggers) to configure how the GraphQL server will behave through a user interface, with no coding involved whatsoever.

That query to send email notifications is then a use case all by itself, and a demonstration of what these features can achieve:

Using embeddable fields, starting from a `Post`, the UI would enable users to compose the notification message using placeholders `{{ title }}`, `{{ content }}`, `{{ date }}`, etc. With the flat chain syntax it gets better, since they could retrieve data from other entities, such as `{{ author.email }}`, or even iterating down from `Root` doing `{{ root.me.email }}`. Then this string is injected into the directive `@sendEmail` (which would be provided by some WP plugin), and added to the schema through IFTTT rules, as I've described here: https://blog.logrocket.com/adding-directives-schema-code-fir...

As a result, the user can install a WP plugin, add `@sendEmail` to the schema through configuration, and customize the email, without touching one line of code.
Which of these options does the author consider the real Holy Grail?

> Once flexbox achieved mainstream browser support, this layout went from "holy grail" to "fountain drink"; it was everywhere, because it offered a great user experience, and was within reach for all developers.

> As the web has evolved, I've discovered a new aspirational layout.
> You have public transpor

No you don't. In 95% of the US "Public transit" is maybe a bus that stops a mile away once every 2 hours. If that.
Former patent goon drives billions of dollars in patent goon business to his door. This is a sex-toy-patent lawyer who got nominated as a West-Texas-oil-country Federal judge and who is advertising to patent troll holding companies to sue the wealthiest companies in America in his court and then so thoroughly denies motions to move the cases to more reasonable courts that he pre-emptively tries to deny any further motions to move such cases because he wants to keep all the cases in his jurisdiction. For reasons.

Nothing suspect about this at all.
My new disruptive startup will TEAR DOWN THOSE WALLS for the wall-less experience
I'm puzzled by this example:

sums = [s for s in [0] for x in data for s in [s + x]]

Why would you do "for s in" twice? Is that intentional? It would make more sense to me if the variables would have been different. And why would you want to add 0 to numbers?! Curious about a real world use case for this.
That's quite a reach and a bad take.

I've only been in the full-time tech industry for about 3.5 years.

Before then I was working hourly jobs to make ends meet, including working half time or more while studying full-time in college, working during high school, etc. This so I could pay rent and tuition with minimal, if any, aid.

I couldn't even afford a car until after graduating from university.

I was walking or taking public transportation everywhere prior to finally getting a car.

I won't disagree that people in SV can be snobby but let's not jump to conclusions here.
https://en.wikipedia.org/wiki/Google_Search_Appliance 2002-2019
Customers have had the option to use bottled water concentrate (and supply their own water) for ages, and yet bottled water use has increased significantly over the last 40 years. I suspect the issue is not that simple.
It would be challenging to adapt in current circumstances with diesel-powered tractors, but electrically-powered tractors might be able to make use of electromagnetic couplings (at least to get the process initiated). You might be on to something for future use.

Good luck with the new attempt. It seems like you're well-armored for the task. Go forth and conquer!
Yes: https://pypi.org/project/backports.zoneinfo/
Compiling the world’s oldest HTTP server and running a blog on it
Video: C Programming on System 6 – Demo Application
Back in the day, it wasn't "very good", at least not in terms of getting it to work. That RK4 in Excel happened because I got extremely annoyed at Octave.
The OP said that using a spreadsheet program can be messy and prone to mistakes, and implied that there could exist alternative approaches. The OP never said a bug in Excel was responsible for the mistake or blamed Microsoft for corrupting the calculation.

In the same sense, one could say manual memory management in C can be messy and prone to mistakes, it doesn't mean that one believes C should never be used in any circumstance, and it doesn't mean one's trying to blame the C complier, libc or Dennis Ritchie for corrupting one's program.

Hypothetically, if someone writes the following reply.

> The C programming language, whether you like it or loathe it, is in such wide use around the world that a NULL pointer dereference would have been noticed a very long time ago. I could believe that there are still many lurking libc bugs with obscure corner cases, but I would bet the memory corruptions were solely due to your own failures.

It would completely miss the point.
No need for a “front end” or “backend” or “pigsqueal”. MS provides a perfectly workable all in one tool, Access, for this kind of work. You can even use Excel as a front-end to access data if you want.
In Germany, there are quite a few cars with "Emergency Assist" technology. There are different variants of it, in my VW Touran it works like this: When the car is in ACC/lane assist mode (similar to Autopilot), it will detect when there is no steering wheel input for a while. First it beeps, then it will brake a few times to "wake you up". Still no input? Then it will brake to a complete stop and turn on the warning lights. In more recent incarnations the car will park at the side of the road.

It is great for medical emergencies (stroke/seizure) but of course you should not rely on it and drive without paying attention to the road.
This is the test and trace system for the worst pandemic this country has ever faced, six months in. I’m sorry Excel spreadsheets won’t cut it.

This is a management failure. PHE has capable coders. And if not, they could hire some.

The NHSX team has managed to write the dang COVID-19 app twice. Once not using the Apple/Google contact API (because management) and a second time properly. It’s all open source and it looks pretty decent.
> year where it is just an arbitrary slice of time we've created

"arbitrary" defined as "based on random choice or personal whim, rather than any reason or system". Since a year is one revolution around the sun, our source of energy, it doesn't seem arbitrary at all.

Between the rotations of the earth (day/night), revolutions around the sun, changing of the seasons, phases of the moon, we basically live in a clock.
Silicon Valley became SV before most of that.

Now it's SV despite all that.
Ooooh. Will the future have Kube Doom Eternal? Kube Crysis 3? Kube (Mortal) Kombat XI?

Infrastructure As Games to make it all fun again.
"The infringing functionality was added to their accused products post June 20, 2017, and resulted in a dramatic increase in sales which Cisco touted in both technical and marketing documents," he added.

Looks like “Encrypted Traffic Analytics” is the functionality in question.

https://newsroom.cisco.com/feature-content?type=webcontent&a...
Congratulations, and great writeup! Compared to other SaaS startups you have seen that eventually fizzled out, what would you guess are the main meta reasons you guys succeeded? In particular, how much value would you attribute to just not giving up at any point? Were there any low morale points on the journey?
Count Down to Your Death
What's your thinking about the case count moving from 90 per year to 800 per year and now carrying most patent cases in the US? Do you suppose there is a West Texas Patent Case Mystery Spot Attractor?
It is a nested loop. I don't find it very readable but the single line formatting makes it worse.
Because I have many tabs open that I am switching between. Some of them work better in full screen and others need less space.
That's all very well for "apps" etc. The vast majority of small businesses provide goods and services. You can't decentralize a grocery store, a restaurant, a factory.

All the world isn't HN.
Will answer more in depth tomorrow. For now: https://pensatingbik.tumblr.com/post/183320546205/learning-l...
I'd concur if s/excellent/adequate/.
The system you describe seems close to Jib [1] or Nixery [2], which are dependency-aware tools built on top of Docker. I think neither they nor the prototype you've described could be as distro/language-agnostic as Docker and ostree/flatpack are. Debian could offer something like Nixery, any distro could, but then it wouldn't be a cross-distro solution.

I personally like appimage, but I don't mind using flatpack because it is so similar to Docker and is also supported on most major distros. Distro repositories aren't going anywhere, and I think flatpack strikes the right balance for users and developers.

[1] https://github.com/GoogleContainerTools/jib

[2] https://github.com/google/nixery
> You're shifting around a lot when driving. Legs moving on pedals, arms and hands wheel turning, head+shoulders turning to look left and right.

As someone who lives in the midwest, I have to disagree. Pick pretty much any random 100 mile stretch of I-70 or I-80 between the Appalachians and the Rockies and the majority of it will be straight enough that you could set the cruise and only have to turn the wheel a few degrees at most as long as traffic doesn't do anything stupid.

When I was younger and dumber I once drove from I-71 near Cleveland almost to Chicago with just my knee on the wheel. There's a kink about half way across Indiana that was the only real challenge.
It doesn't do what you think it does. From https://www.python.org/dev/peps/pep-0616/#rationale

"There have been repeated issues on Python-Ideas [2] [3], Python-Dev [4] [5] [6] [7], the Bug Tracker, and StackOverflow [8], related to user confusion about the existing str.lstrip and str.rstrip methods. These users are typically expecting the behavior of removeprefix and removesuffix, but they are surprised that the parameter for lstrip is interpreted as a set of characters, not a substring."
Lots of great improvements. Sadly I won't get to enjoy the new string methods, dict operations and generic hinting as I'm still stuck writing code that should be compatible with older versions of 3 (and 2.7 but six takes care of that).
Tools I use: argparse builder
I recently played around with a lib called Detectio which was super fun and met my needs.

Like you, I have barely any ML experience so it was nice to be able to still finish what I set out to achieve.

I write a simple tutorial and sample code base -> https://ajaxdavis.com/post/An-Open-Source-Computer-vision-mo...
Personality disorders leave a huge wake of destruction when untreated and unrecognized. Also they are problematic and lead to a lot of hurt even when someone is recognizing the problem and working on it. Something that gets lost frequently in the dialog is the value, a seemingly critical value, that these people contribute to society even if it's at a great cost. A lot of times, especially in our current world climate as conversations about this topic grow, we otherize people who suffer from these conditions. IMO, that is dangerous. It creates a stigma and decreases the likelihood for a person with these conditions to allow themselves to see it for what it is and let it fester into constant malignant destruction of themselves and anyone near them. I personally steer clear of people with NPD/BPD. I was raised by someone with NPD and as such I can be kind of a magnet and ill equipped to set boundaries. My point is, people should educate themselves on the conditions and set boundaries and do their best not to enable, but those that can should encourage sufferers to acknowledge and integrate their disorder to reduce harm and utilize their unique minds in a way that takes other lives into account. Dialectical Behavioral Therapy does wonders. I realize it's almost being a human sacrifice to help someone with NPD or BPD transition thought patterns. I don't wish it on anyone... but someone's gotta do the work, this part of humanity isn't going to go away.
Academically (And, to some extent, practically speaking) Orleans Virtual actors aren't the same as Erlang (or Akka) actors.

Major differences:

- Normal actors are pretty flexible, can work in local or remote contexts. Orleans is probably best described as Sharded Actors, It's a 'guided' implementation of Actors compared to Erlang or Akka where you are given a toolkit and have to build out what you intend to do.

- Orleans doesn't have any ordering guarantees. While this is not a firm requirement of the Actor model itself, both Erlang and Akka guarantee ordering between a given Sender-receiver pair (i.e. messages sent from A to C will be sent in order)

- Akka and Erlang have the concept of Supervision. i.e. An actor may have a child, and if that child crashes, the (parent) is notified and may choose how to react (restart child, don't restart child, crash itself)

- Orleans may allow more than one activation of the same grain at the same time. A stable and properly configured Akka Shard cluster will never have more than one of the same entity actor alive at a time.

- Orleans can magically scale out with the cloud (If you're running them on Azure.) Erlang/Akka you'll have to deploy your new nodes.
For some reason, I find the writing and decisions to be mature. Shouldn't the early stage product development be messy and full of doubts? I understand the post doesn't capture everything, but it feels the decisions the founders took most of the time had positive outcome. Is this luck or value of product-market fit?
typed users_y1KGkRi and y1KGkRi. Got one result, for a link shorten-er app
Blockchain Music Companies You Should Know
Then don't buy it?
I only ran into the Orleans Virtual Actor model a few days ago. I have an application I long wanted to move to a distributed model, and I've been struggling with seemingly to reinvent everything due to an unusual execution model.

So it was quite an eye opener to read about how Orleans introduced Virtual Actors, activations and placements of actors and how these are exactly the things I've thought about over the years. I've read about e.g. the classic Erlang actors, but the concept of virtual actors in Orleans really fit my model.

I'll be sticking with Python, but starting with the Orleans paper has lead me to quite a few similar systems: https://www.researchgate.net/publication/233416056_Orleans_C... that reference it.