skysight-inc/HackerNews huggingface dataset:
I really don't want to argue, I'm just saying I remember a time when a 2,3 year old computer was worthless.. There are videos of people playing modern AAA game titles (on low settings of course, but at 1080p) with CPUs from 10 years ago and GPUs from 5+ years ago.
We believe Tesla is 1-2 years ahead of us, and that's held fairly true since the beginning of comma.
For any thing else I recommend ExoDos Collection. It is amazing. I want to build a room in my house dedicated to it.
Unsure of how you extrapolated the total number of users from my previous statements. We were a B2B SaaS where our customers each served 10,000s of end users, who also had access to our platform with their data stored within. In aggregate we’re talking 25mm+ total users in my case.

At the time, being that the DPO role was new we didn’t know how many requests to expect. And while the law may allow for 30 days, our customers wouldn’t take it well if it took us longer than a couple days (our customer service SLA was 24 hr first resolution time). Their customers would complain to our customer who in turn would complain to us. If we make our customers look bad, we hear about it loudly and clearly.

To each their own, I suppose. From my perspective as an overworked founder, with a small team, growing at >200%/yr, we didn’t see the need to take on additional work just to maintain a very small revenue stream

I don’t fault companies for wanting to remain in the EU market, but for us, it didn’t make much sense at the time as our real growth opportunity lay in the Us/Canada (mostly due to consumer habits in the region).

I have no issue with the spirit of GDPR, and as a human, I support it personally. But, for my business at that point in time, it didn’t make economic sense to comply, so we left.
This is going to be interesting for apps obeying desktop ui settings. But running any software on any platform might make up for it.
>> Web development takes the lion's share of computing people pay for which translates to the work people will do (we need money for survival)

This just isn't true. There are so many systems where the web component is just the tiny part of the iceberg you can see, but underneath some form of browser client there's a huge mountain of computer-based technology. Concepts like containerization and microservices are far bigger than the notion of current web development.
>The code was likely written in the early 90s

This is easily falsifiable by running a test case (create 1000 icons on desktop) in windows 7, 2000, XP and 98.
Big Dummy's Guide to the Internet Edition 1.1 (1993)
In the amateur radio community, hams who pass away are known as "Silent Keys," a reference to a telegraph (Morse Code) key that is no longer being used. The phrase is poignant to me.

At 61 years of age passing away is for me a thought that appears more and more often in consciousness. Yet it's not scary or something I dread.
What storm? Generics?
Lithuanian car rental company Citybee leaked details of 110000 customers
> Many Americans view our federal government poorly, on both sides of the aisle

One side believes that government can be, and should be, improved by collective effort.

The other side believes government cannot be improved because government itself is per se bad.

There is zero equivalence between the two.
Oh sorry, I thought your complaint was about having to phrase things as sentences. Yeah, Siri is pretty stupid about inferring that the number after hours is minutes.

Parsing time related stuff in general seems to be an issue. "Set a timer for a minute fifteen" makes an alarm named "Timer" set for 3 PM.

But if you say "Set a timer for a minute fifteen seconds" it works fine.

Curious if anyone else can duplicate the "a minute fifteen == 3 o'clock" issue or if it's somehow hearing me wrong.
The main repository seems to have been taken down but it is still available at https://github.com/kmcquade/endgame and on Pypi
The use case is not needing to wrap your code in an IIFE [1] when you would have a top-level await statement. It is useful in entry point of apps where you might need anything that uses async. It's also useful for having async modules. [2]

They're also very helpful for debugging. Using await something in the console is way more convenient than something.then().

[1] https://developer.mozilla.org/en-US/docs/Glossary/IIFE

[2] https://github.com/tc39/proposal-top-level-await/blob/HEAD/R...
FWIW, Oracle is a great place to just do a 9-5. Their compensation is competitive with FAANG, their health package is ridiculously good, and you can pretty much do anything you want, so long as it doesn't cross division lines.

You won't change the world there, but you will work on interesting projects, have good job security, and you can put your work down at the end of the day.

Source: Acquired by Oracle, left shortly thereafter because I believed I still wanted to change the world.
In that case, I post the 5-star review, claim the $100, delete my own review, and post negative seller feedback.
>someone committing a crime should still face the consequences regardless of what they are fighting for.

This was literally the entire point of the protests. Way to miss the point.
Almost all companies will sell the Bitcoin as soon as it's paid, yes, most without ever touching it themselves. It's just like using a credit card as far as they're concerned. See this chart from BitPay on how they work: https://support.bitpay.com/hc/article_attachments/3600338995...

Remember that every actual Bitcoin transaction requires, on average, paying a $17 transaction fee to pay all the miners and the electricity they used in processing the transaction, so you don't want to actually be sending it between people often.
Peroxide is a surprisingly good stain and odor remover. I prefer it to vinegar because it doesn't have a pungent odor that masks the odor you're trying to get rid of.

But yes vinegar is awesome. It's fantastic at water stains like nothing else.
Could this possibly a bug when the author committed some recent changes? It's worth giving the benefit of the doubt here.

But yea, I had to do a triple take with my jaw dropped. Grateful for Firefox's Reader mode.
Not a clone but you can download the code from here:

https://pypi.org/project/endgame/#files

I was thinking about putting a new repo with the code in it but I'd rather not risk the wrath of AWS since my job kinda depends on the service. Which probably says something about the state of Faang companies that I'm even concerned about it.
> That's clearly not what nerdponx meant.

I disagree. I made a straightforward interpretation of what was written. Given what came after the part I quoted, you really have to stretch to interpret it differently.

The OP underscored the same point using profanity.

I made a response that was clearly sardonic, attempting to be funny.
Yes, the proposal was accepted this week: https://golang.org/doc/faq#generics
https://ftp.sunet.se/mirror/archive/ftp.sunet.se/pub/simteln... and the ZIP files in there seem to work for me
At some point there were restrictions of getting money out of the country; a big, well known American company with business in Nigeria bought a mix of cryptocurrencies with local currency and sold it for dollars, getting around the restrictions. The transaction was in tens of millions of dollars, if I recall correctly. This kind of transactions make the local currency even weaker, so there is at least this reason the central bank wants to close the door.
I assume the key aspect here isn't to provide an alternative storage mechanism (since the cookie laws aren't actually about cookies themselves, but rather storage), but rather to provide a mechanism with clear and centralised user control. Users must opt-in, so its good in the eyes of the laws, but the advertisers get the benefit of easy legally-compliant tracking when a user allows it.
So your solution to build systems has absolutely none of the benefits that build system do in fact bring, or the ecosystem of a language that you might consider terrible but actually has a decent amount of quality re-useable code. But this works for your very specific use-case?
I'm quite sure they were.
As a lifelong US resident across about 10 different states, I disagree very strongly.

In mid-sized cities and large urban areas, the police are generally extremely corrupt and integrate with high level politicians and corporate interests for bribes, carrying out policing actions to serve cronyism, etc.

In small towns, police typically align with small town politics and specific locals with political power, ranging from judges to attorneys to business owners. If they decide you’re on the wrong side, they’ll find reasons to harass you, use speeding tickets, littering, frivolous fines, etc. Of course this often affects underrepresented groups, but can easily affect people in the majority if they just don’t like you.

Most communities see the police as a group to strictly stay away from. You hope that in a real emergency they will do their job, but more often they are just authority theater looking for a way to jam you up or exploit you. They absolutely are not good natured community members by default, and even if some specific cop is trying to do right by the community, nobody can assume that is trustworthy and everyone has to just stay away.

Policing, especially the procedural mechanics of fining or arresting people, is just fundamentally broken from first principles in the US, and most police systems exploit this for corrupt gains and abuses of power. Exceptions are so rare as to be ignored and assumed irrelevant.
Thank you!

This is the first place I've seen this acknowledged - and, bizarrely, I read most of the PRs and commits to the `safety` part of Panda, and didn't find a single reference to the checklist in that Medium post (and, only some of the requirements seem to be implemented in most cars). It feels really late to me to be doing this, and it seems like they could use a good docs person and some, well, leadership in the project.

One thing I noticed in general was that it seems like most Comma communication is side-channeled - most commits and PRs do not have much of anything in terms of description or documentation, and code review is really sparse, it feels like there's a back-room discussion happening rather than GitHub, presumably on Discord? This makes it almost impossible to understand the safety constraints and reasoning, or to audit changes to the system.

But, it also sounds like they could very well be on the right track for 1.0, provided they hire the right person and they're able to clean things up.

Thank you for pointing this out, cheers!
I may well be wrong. Really not a hardware guy. Just super happy to have something that feels much snappier than my macbook and can run doom eternal for a few hundred euro
Holy moley, $35K (after discount) for the top of the line box. Maybe I'll look around for a used one of those in about 10 years.
I agree. It's easy to grouse about web development and forget the bigger problem web development attempts to solve: how to send or receive data (or kick off a process, or react to some event) from any computer (or phone) in an human-friendly way.

This is a big area to wrap your head around. Best practices continue to change, risks change, technologies change, the scale of demand can change. It's complex.
> We all agree the JS ecosystem sucks.

I mean there's a lot of garbage out there as with any ecosystem but saying "we all agree the JS ecosystem sucks" reeks of immaturity.
The less effective the status quo is, the more willing people are to try radical approaches, be it technology, politics, dieting, etc.

In my own small world of political banter, the number of people who have floated, or not disagreed with the concept of balkanizing the U.S.A is astounding. When I grew up, America was the greatest country in the world, and now my friends say - well we tried. Maybe balkanization would be easier since nobody can seem to agree on a damn thing, not even the budget!

The farther apart the two sides of the political sphere, the less the work together to actually produce tangible results for the average American, the less happy and healthy the average American - the more likely we as Americans are to support a scrapping of it all and supporting Communism, Anarchism, Direct Democracy, Fascism, Theocracy, or other ideologies, and not Republicanism (that is, being a republic).
Why would anyone care if they violated YouTube's terms of use?
> I'd rather Google not spend their project's resources on never-buyers like yourself and instead spend those adding features and driving cost down for people that could be genuinely interested.

Sure. And drop all open protocols and support only the proprietary ones while they're at it?
The spirit of the law dictates that:

- The default option of consent is opt-out.

- Opt-in and opt-out should be equally easy and accessible.

Tell me how a company who would be trying to be ethical and follow this spirit would come up with the current pop-ups.

Don't blame the legislation for allowing dark patterns to be used due to loopholes or failure of prediction all possible clever tricks to circumvent the spirit described above.

It hasn't unconditionally failed, the pop-ups are still there and I opt-out of every single one of them.

Except one: schneidersladen.de - they follow exactly the spirit of the law, I put the bar there.
Hello! I'm the author of this post wave
This is part of my point — the majority of software time and effort is spent on web-and-related software.
Arte is spectacular. I've been a fan for a while, and it keeps popping up good surprises.
Things change at a rapid pace in startups. So long term planning could be seen as useless. However, one could argue that without long term planning it'll be extremely difficult to build anything.

So you must have a vision. What is it that you trying to build?

Then the step after that would be build something you can get in front of users and get feedback.

That's your first 3-month strategy

Second 3-month strategy would be to build on that. Build the prototype and show it to more users.

After you've figured out the product a little better. You can start doing longer term planning. 6-month plan would include building a product further, getting feedback, getting first beta users, building a marketing engine.

You should always plan if not for anything else but to keep you on track. Even if it's the wrong direction, with a plan you'll know sooner than if you just keep wondering around with purpose.
tru.ID announce £3M seed round to reimagine mobile authentication
I mean the value prop is the software functionality, not the storage. You think lastpass/1password are funding their development with a markup on storage?

I can get the argument that it’s not worth $36 but not because of storage costs.
I think people have different definitions of "upper class". Maybe "Upper-middle class" would have been a better term, since pretty much everyone in the U.S. calls themselves some flavor of middle class. But my point is is that most people are not doing nearly as well financially as a mathematician/manager working at Westinghouse modeling nuclear reactors[1][2]. For example, 70% of americans have less than $1,000 of savings[3].

[1] http://www.paulgraham.com/work.html

[2] http://www.paulgraham.com/credentials.html

[3] https://www.fool.com/retirement/2019/12/18/the-percentage-of...
But is that really bad for Go? I'm not sure it is. Go1 will always be useful just as it is.
Vietnam might not be as bad as China but it still doesn't exactly have a stellar human rights record.
>Go is still my favorite language when it's the right tool for the job.

Forgive my ignorance, when would you recommend go? As in what problem domains have you seen it excel at?

I have thought about trying it in the past and even tinkered with a project for a bit but didn't quite find it useful enough to be worth the tooling cost (at the time). Would like an excuse to check it out again.
This. This right here.

If it didn't get forcibly put into people's hands, it probably would have died on the vine.

One of the things apple's always understood is the idea of "across-the-board" availability. Take some specialist part, like, oh, say, a mouse, or a sound card, and make it so that all of your machines ship with it, period. It's the new "lowest common denominator". We had mice back in the DOS/Apple II era; good mice, even, it's just that nobody wrote anything that supported them (outside of a few specialist apps like some art programs), because only a few really rare people had them.

When apple made the mac, they'd learned this lesson, and made it mandatory - this is actually why they initially refused to put a CLI into the thing, even though their own MPW dev tools had one: they wanted to make it more difficult to do cheapass ports of stuff like VisiCalc than it would be to build a new, gui-based program to solve the same problem from scratch. (Amongst other things, this open-field helped a certain company launch a new gui-based spreadsheet app called Excel, which has done rather well for itself.)
No, I think both sides have an idea of the perfect government. It's just that the ideas differ radically (in fact, they are mutually incompatible). So we get the current situation, where neither side is satisfied with what they have. And I fear the degree to which both sides think they have to destroy the other side in order to get what they want...
evanw appears to be Evan Wallace, the cofounder and CTO of Figma (!?)
Data Processing Support in Ray (PySpark,Dask,Modin,Mars)
One Thing - Jetbrains IDE or anything else where you can configure a ton of options.

Have a cron script to constantly export the preference file and sync to cloud or local NAS.
GLP-1 and Obesity
End-to-end 360 video production: recording, editing, stitching
This stood out to me:

> As announced in the Go 1.15 release notes, Go 1.16 drops support for x87 mode compilation (GO386=387). Support for non-SSE2 processors is now available using soft float mode (GO386=softfloat). Users running on non-SSE2 processors should replace GO386=387 with GO386=softfloat.

This change makes perfect sense to me (you'd have to be running a 20+ year old CPU to still need x87 float support, and plenty of distros have already dropped it), but I'm curious as to whether it was partially motivated by Go's decision to implement their own optimizing compiler and surrounding ecosystem. Modeling x87 is a real pain, one without obvious benefits when outside of a mature surrounding framework (like LLVM or GCC).

Can someone with knowledge of Go's compiler internals opine on this? It'd be interesting to hear which bits are sources of historical pain/relative ease.
It's being downvoted because the US, with some very narrow exceptions, does not recognize a right to not be filmed in public (or filmed in private if the filming location is from public property). As gross as it is, if you leave your front curtains open, I am (legally) allowed to film through your windows from the sidewalk.

Since this is an article about a US movement, US police, a US company and US laws, it is fair to downvote contextually wrong information.
This reminds me of the time, about a month after Napster went offline, my boss nuked a co-worker's hard drive because "the music downloads folder was making the computer slow." He typically claimed zero knowledge of computers, and left such matters up to me or his buddy that owned our ISP... but on a weekend, he took matters into his own hands and destroyed a huge compilation of irreplaceable tracks. I'm still offended by the senseless destruction to this day, even if I don't personally value Phish to that degree.
Exactly. So many people want to seem enlightened and "above the fray" and blaming "both sides" is an easy way to sound smart and perceptive.

Only one side attacks democracy and government as concepts.
To that I find that the answer is usually: find ways to avoid needing to sort the list! This is more viable for many problems than you might otherwise think.
>Wasn't it just a few years ago they found microbes underwater where there wasn't any sunlight?

It sounds like you're talking about the life around hydrothermal vents[0], which ultimately depends on chemosynthesis[1]rather than photosynthesis. This has been known since the late 70s, and actually fuels significant macroscopic life[2], not just microorganisms.

There's also deepwater life surviving off of things like marine snow[3], which is nutrient carrying detrius from the surface, or whale falls. But both of those ultimately depend on photosynthesis that happens near the surface.

[0]https://en.wikipedia.org/wiki/Hydrothermal_vent#Biology_of_h...

[1]https://en.wikipedia.org/wiki/Chemosynthesis

[2]See giant tube worm, for example: https://en.wikipedia.org/wiki/Riftia_pachyptila

[3]https://en.wikipedia.org/wiki/Marine_snow
Of course this was going to happen. Who knows, probably this way the author achieved what be wanted and those policy exploits will be revisited, at last.
Excited for io/fs. The design work that went into it is hopefully going to lead to the level of interop that we see with io.Reader and io.Writer.

It's nice to see the float parsing speedups too.

I do wish the Unicode package wasn't tied to the Go release cycle. Unicode 13 was released in March of last year.
Ok, so basically I have to look for a new password manager.
I think its a bit of a greenfield thing. In the early days there was new interesting things to do everywhere you went. Now a lot of the low hanging interesting fruit has been picked, and you have to go deeper to do interesting things.
Wait... Alexa enabled microwave? I am genuinely interested in what the point of that is.
> But is that really bad for Go?

No, I don't think so.
I was worried when LastPass was bought up by LogMeIn, but stuck with it. Then LastPass tripled the price. I went from a premium to a free tier user. Now LastPass pulls this, and now I'm not even a user. Hello premium BitWarden.
Sure, but how bad can it really be? It has existed for like 60 years and those people are still living to be 80.
Apologies. Wound too tight today.
Two points:

Your calculations assume that attackers are interested in brute forcing one particular token. But if your app issues a lot of tokens then it becomes easier for an attacker to find some valid token.

For example, if you issue a billion tokens and allow a thousand requests per second then I can find one of those tokens in about 100 days. Is that realistic? Maybe not, but it’s a lot lower than 250k years.

The second point is that I’ve several times in my life seen code that logs a hash of a security token to allow easy correlation of requests. Such a hashed log is then vulnerable to offline brute force attacks with very many more than a million guesses per second.