skysight-inc/HackerNews huggingface dataset:
Polish prime minister just said there are two labs ready ... while hospitals are sending samples to Switzerland. Health minister ensures full monitoring of incoming travelers ... while nobody even measures temperatures of people disembarking planes from China (direct China air connection is still open), nor Italy. Chief Sanitary Inspector popped in TV yesterday proclaiming ordinary flu is more dangerous. AMA with staff of one of the biggest capital hospitals: no procedures ready, no PPE, about 70 empty beds for 2 million population. Full denial.
Uber and Lyft have a new ride-hailing rival in Myle
> Speaking at the BlueHat security conference in Israel last week, Microsoft security engineer Matt Miller said that over the last 12 years, around 70 percent of all Microsoft patches were fixes for memory safety bugs.

https://www.zdnet.com/article/microsoft-70-percent-of-all-se...
> leveraging elastic compute costs and kubernetes "self-healing"

The indirect effect of building on a system like this is that the recovery mechanisms get tested on a regular basis instead of just on the odd day when things fail.

Spot instances are like a natural chaosmonkey mode, with money being saved and forcing you to build failure tolerance, retries & circuit breakers early in dev.
Most (?) RDBMS query planners rely on updating statistics on the data in the table to decide what type of joins to perform.

I can imagine cases (distributed databases, different speed storage) where it would make sense to test the queries and learn which optimisations make sense. It'd be self tuning and able to adapt to changing hardware.
I thought that HTTP error code was the joke...
> As soon as they cease being lightweight (and the norm seems to be more effort spent creating mocks/stubs than the actual tests) then they fail even in that purpose and just become another impediment to useful work.

Agreed. I think that in many cases it is a signal that your code is too complex, and may be violating the Single-Responsiblity principle.
Raspberry Pi 4 can handle a wider range of USB adapters thanks to revised design
Even if it were 17%, that ignores impact. Impact of a bug in C is very often, at best, taking the entire service down, and at worse gaining full RCE.

I also think that a percentage is a weak indicator in general. With bug bounties we're seeing a massive influx of vulnerability reports for exposed APIs - this is almost always XSS and CSRF. I am not discounting the impact of those vulns, only saying that percentages are very market driven.
At this point not really. As soon as that browser started to gain traction I'm pretty sure that the company would cash out to the next highest bidder and sell any and every scrap of information they find valuable.
DNS-over-Wikipedia is my goto strategy for websites like this (Scihub, Libgen, Piratebay, Popcorn Time, etc.).
> Applets and plug-ins were so much more capable.

Except that they couldn’t alter the DOM, or handle events on DOM elements, the two things that developers really needed (even if they didn’t know it).
Perhaps an association of folks who share fundamental values? Nah, that's crazy talk.
The page was using zeit 1.0 before, which means it was a container and not a serverless function. (I know you know Rauchg, just explaining for other people). This container was actually failing because of rate limiting by wikidata causing an unhandled promise failure.

I had made a fork of this to show it working on zeit now 2.0 with 'stale-while-revalidate' so that it only update once every minute. But obviously I took that fork down once I saw this comment.
Yes, I know… that's why I said possessive "its" has no apostrophe.
This is pretty common, databricks for example uses regular instances for the driver and spot instances for workers by default.
To be honest, I was using JavaScript for years as an OOP language before I actually understood how I could use JavaScript as a functional language.

However, I don't think the limitation was the language. The biggest limitation really were bug ridden browsers. Trying to get something to work across all browsers was incredibly challenging because so many basic features simply didn't work.

Had the syntax been based on scheme, my guess is scheme's reputation would have suffered. I think people have a tendency to blame the thing that they understand the least, so I could see people blaming scheme for the browser's failings.

Also, I went to a university that taught SICP and I'm sorry to say it wasn't popular. Again, when things didn't work, there was a tendency to blame the thing that was least understood.

I could see a Lua-like syntax being approachable, but even that wouldn't have helped. Again, the biggest problem with JavaScript was being tethered to buggy browsers that often failed when you asked them to do simple things.
The T2's job is to bring the main processor out of reset. The actual booting is standard UEFI, apparently.
Because Grindr is two guys....
The Power of 10 Playbook – Daniel Gross
Apple has been moving their defenses earlier and earlier in the boot process. According to this talk[0] they are even able to foil malicious option ROM[1] and other early boot attacks. I don’t recall if they mention boot passwords specifically, but they claim to lead the industry in this regard.

[0] https://youtu.be/3byNNUReyvE

[1] https://www.blackhat.com/us-19/briefings/schedule/#behind-th...
Good point about the "slight" wording, though I don't necessary agree that it can get much worse than 2x, with actual workload that:

- could be more I/O bound than when just doing PK lookups with pgbench

- could be getting a wrong plan from the query plan cache if named prepared statement is used
Neither is “great” on a GPU:

• Image optimization is still mostly software: JPEG, PNG, WebP. GPUs do not bring much to the table here at all, and consume a lot of power, which is likely to upset the hosting ISP of that cache node.

• Video encoding is better, but still average. NVENC (Nvidia’s encode Engine) has some quality challenges and limitations.

Further, doing this at the edge makes less sense: if you have to fetch the source material from the origin, do the heavy lifting centrally and store the results at the edge. Storing 4-5 renditions is cheap compared to GPU running costs here.
Sure there is. If the accumulated doses over time aren't unlikely to significantly harm someone before they die of something else, then it's safe.
I remember Gmail invites. Ironically, Evan Williams (formerly of Twitter, now of Medium, at the time working at Google after they bought Blogger) was the person who sent me mine—and on the morning of April 1st, 2004. So I've had a Gmail account since the first day it was publicly available.
Something like TCL would be far better. Or Inferno.
This is a good point, it’s easy to forget about how closely watched Microsoft was by regulators.

But IMO it makes it all the more surprising that Microsoft doubled down on the centralized OS+API+apps leverage combo that had brought upon them the antitrust scrutiny, instead of dispersing their influence?
Certainly not all deployed resolvers support DNSSEC; that goes without saying. I’m sure there’s lots of old software out there.

However, it’s likely the majority of resolvers that have been deployed in the last few years support DNSSEC, even if it’s not (yet) enabled.

And certainly the users of 1.1.1.1, 8.8.8.8, 9.9.9.9, etc. are using DNSSEC-aware resolvers. So the number of users of DNSSEC-aware resolvers will only continue to increase.
I saw that too, but there is another bullet point about the implementation experience of trying to use Go to implement some system services. Sounds like they had a bad experience.
Same in Australia
Why aren't you writing a kernel in Rust?
One of America’s Boldest Housing Initiatives Has Reached Its End: Did It Work?
I'm curious if TPM measurements would catch these kind of manipulations. It's probably system specific but the configuration of the BIOS should (as far as I understand it) be captured as part of the measurement process.

If requisite credentials or remote attestation is sealed against a certain measurement value it should protect the system.
Indeed, it could also be higher..

Wishful thinking doesn't really make it so :)
(Even though I really wish it did)

Whether it matters in practice I don't know.. how much can we really do ?
Why not use spot fleets to solve this? You can specify multiple acceptable instance types.
- Tcl/Tk

- Perl5

- Python

- VT220/VT100 terminals + ncurses
You fixed it! So much better :) Awesome project, definitely sharing with friends.
Does the macOS resolver support it? Does the iOS resolver support it? Does the Android resolver support it? Then: not so much with the "majority deployed in the last few years".

People using 8.8.8.8 aren't using DNSSEC; their "DNSSEC" is a single bit in the response header that says "yes, we promise, we did DNSSEC".
I have a non-technical friend who says Dragon is too unreliable to be usable. My intuition was that the problem is probably somewhere else and that if Dragon doesn't work nothing will. I'm under the assumption that competing voice recognition software competes on price. Is that assumption wrong?

(For example, I suspect the microphone their school supplies them with may be no good)
Yes, had one from an uncle.

I then realised that I could invite a second account, so I created a handful of accounts and still own them today.

Good times.
Docker is pretty much abandoning Swarm though, so wouldn't recommend that at least.

https://www.bretfisher.com/is-swarm-dead-answered-by-a-docke...
Whoever wrote up that specification list for the Developer machine deserves a raise. You can hear the MBAs already talking about how much more needs to be raised next round in order to pay for these.
same in san francisco
I use a powerball
Distribution is a vastly underestimated economic problem. Of course, politics can be a major factor too, but I wouldn't assume that politics is the problem just because there is plenty in one place and scarcity in another.
Verification of option roms as a part of secure boot is a part of the normal uefi spec, however some vendors forgot to implement it

https://docs.microsoft.com/en-us/windows-hardware/manufactur...
Yet, Amazon won't let me review the mystery novel my wife wrote.
PS: I work at Elastic.co.

At any point of time, if you feel that docs are not appropriate kindly raise a issue in https://github.com/elastic/docs. You could also consider contributing to docs. Appreciate it!

Other than that, we have a very live discourse forum. You can also put up all sort of questions discuss.elastic.co.

Still want a more real time chat, you can join slack group too ela.st/slack.
> I haven't interviewed there, nor will I. Realistically I won't pass the interview

Then isn't this ideal? You don't waste their time and they don't waste yours?
On the one hand, building fault tolerant infrastructure that can, as a side effect, work painlessly on spot instances is great.

On the other hand, you can purchase reserved instances and get ~60% cost savings with zero engineering work. Its worth thinking long and hard about whether the cost of engineering time is worth that next 20%.

There's also a lot of useful ground in between "critical state, must never be lost (like a database)" and "can handle being terminated with 2 minutes notice". A service that can be re-created if necessary but takes 10 minutes to start up is really scary if run on spot instances, but can still be pretty useful.
This is indeed very cool content! The type that keeps me on this site. I too am constantly shocked by how many reverse engineering articles. The patience and knowledge required is insane
It's worth noting that Go and Dart were characterized as "highly productive" whilst Rust wasn't.
The complexity is mind boggling. Physically, we are not what we were a few months ago. And what exactly is physicality?

People were commenting that the idea that every cell is replaced in a living organism is 'laughable'. Brain cells and osteocytes were cited as examples of cells that are never replaced.

However, I still think, and more strongly than ever, that brain cells and osteocytes can be examples of unchanging cells if an only if it is proven beyond a shadow of doubt that every single atom constituting such cells remains intact during the lifetime of such cells.

Since the human body is subjected to a lot of physical stress and damage and repair is continuous, it is possible that damaged brain cells or osteocytes get replaced with new ones. Need to read more about this, though.
As your source indicates, it was Microsoft that stonewalled ES4. By the time Adobe agreed to let it die, it was a capitulation that they had been vetoed.
So, Smalltalk/Pharo.
Yes, all Intel X86 CPU's start up in 'real mode' which is 16-bit mode.

They start this way because at initial reset none of the required data structures for protected mode operation (page tables, GDT, IDT, etc.) are present. So the CPU starts up as a very fast 8086 who's purpose is to setup just enough page tables, a GDT, an IDT, etc. to be able to switch into protected mode and continue system bootstrap.
Js_of_ocaml [1] is a good alternative to BuckleScript for standard OCaml (non-Reason).

For example, it works well with Core_kernel [2] and Async_kernel [3] to provide high-level functionality that is cross compatible between Unix applications and browser applications.

[1] https://github.com/ocsigen/js_of_ocaml

[2] https://github.com/janestreet/core_kernel

[3] https://github.com/janestreet/async_kernel
> I'm convinced I'm probably smart enough for at least a handful of roles there

There's a scene in Zero Dark Thirty where the CIA chief asks a subordinate for an assessment of another agent. "She's smart," he says. The chief shakes his had and replies, "We're all smart here."

Google has 0 need for more smart people to apply. They have all the smart people they need and then some. What they want are people who will do whatever it takes to work at Google, regardless of the hassles of applying. Then they find the smart people in that group and hire them.
https://help.okcupid.com/article/59-how-to-use-match-search

> Monogamy status

And then of course every single dating site lets you write custom descriptions. (Though IMO it's fair to assume monogamy since that is the overwhelming majority. [1])

[1] https://www.npr.org/2019/02/18/695731314/the-new-sexual-revo...
I agree with your summary.

My worry comes from the fact that a computer system of the scale of Fuchsia comes up every couple decades.
I'd like not waste another one on C++ shortcomings and Fuchsia going with Rust was a great chance for a better dominant language in 20ties.
Google IMHO is a waste of time.

B average overall in Comp. Sci, completed BS degree in 3 years at UT Austin, Google contacted me after classmate and I registered for Google Cloud TPU to complete a class assignment faster using Google's hardware, rather than use slow old CPU's in school labs.

Interview did not get farther than email us your transcript first (Google doesn't waste time with you unless you are nearly or all straight A's).

Anyway, who wants to work on the West Coast where 30% or more of your salary goes to rent and high living costs ?

Instead I interned at a major fortune 500 hardware co my last summer and built them a web based "panel" that their engineers could use to test hardware layers. My manager showed it to his manager and before I even started my last semester I had a decent offer from them (Austin).

More importantly, I have work life balance, don't have to show up till 9:00am, nobody works over 8 hours a day, no weekend work - - - but my Mom just signed on with Apple in Austin and they are working her like a dog.
One reason I stopped using was it turned from delightfully light to painfully bulky. Also its deliberate transition (I’m sure they had reasons for that) from a simple chat app to more Slack like.
I don't know what else to tell you. "Responsible Disclosure" was literally a coercive marketing strategy cooked up by vendors; it isn't a term we arrived at organically. Don't use that term. Use any other term you like, but the convention in the field is "coordinated disclosure".
This is a common headline but Blockbuster would only have delayed the inevitable by buying Netflix. Netflix was a money loser and Blockbuster could not have carried it for too long before it closed it. And eventually, another company would have succeeded with streaming. Profitable companies can't carry dead weight for too long. Either the board will replace the CEO or the shareholders will start to make noise and have the company change course. A common strategy of takeover raiders is to close all unprofitable units and goose the earning so the stock will rise. They never look at whether a unit is a good future investment.

Blockbuster even started its own Netflix competitor but they could not spend the money and time to make a go of it.

The only reason that Netflix is still alive is that investors believed that eventually, it would be profitable. It took many years. Blockbuster did not have the luxury of waiting until Netflix succeeded.

So no, the idea that Blockbuster missed an opportunity is not correct. It never had a chance.
Learn OCaml in Y minutes: https://learnxinyminutes.com/docs/ocaml/
Dr. Noritaka Kobayashi – CEO of Bajji Inc – AsiaTechDaily
> Saying people love JavaScript because it’s the most popular

I’m sure it gets a lot of hate just because of its dominance.
You need to enable regular expression.
Ever?

Browsers have been free for personal use for a _long_ time.

Here, see the announcement for Netscape Navigator (October 1993) [0]

>Customers who download the software do so for personal use only. Commercial users can purchase supported, licensed copies of Netscape directly from Netscape Communications. Pricing starts at $99 per user, which includes a 90-day warranty and customer support. Volume discounts are available for multiple user licenses. For information on volume licensing of Netscape, send electronic mail to sales@netscape.com.

[0] https://web.archive.org/web/20061207145832/http://wp.netscap...
IIRC last official news I heard from Fuchsia is that it was an experiment to test OS features.

Is this is still the official position?
Oh it saddens me so much that Rust is not approved for kernel development, oh well.
The Rock considered as a kind of rock
Dating is absolutely not a 'market for lemons'.

Also, the most highly trained academics are woefully unqualified to make matches. Socially attentive individuals in the relevant age cohort fare probably a lot better. A lot of women, in particular, are half decent at guessing, among the people they know, who might make half-decent matches, partly because they actually know their peers.
EmberJS Gets a New Website
It’s been at least three years so it’s difficult to do a real write-up. In a lot of ways it was death by a thousand cuts. But some things off the top of my head:

Having to rewrite or copy/paste data structures for different types, given the lack of generics. As I understand it, even Google now has tools that generate go source from “generic” templates. This is absurd.

Defer to free resources (e.g., closing files) is a terrible construct because it requires you to remember to do this. You have lambdas! Use them so that the APIs can automatically free resources for you, like Ruby and Rust. It’s insanely hard to debug these kinds of issues because you run out of file descriptors and now you have to audit every open to ensure matching closes.

Casting to interface{}. The type system is so anemic that you have to resort to switching over this, and now you lose type safety. Combine this with the compiler not caring about exhaustive switch statements. And combine this with interfaces being implemented implicitly, and it’s a mine field for bugs.

I literally had a go maintainer waffle on adding support to calculate SSH key fingerprints because “users can just read the RFC and do it themselves if needed”. This is an indefensible perspective on software development.

Despite “making concurrency easy”, having to implement concurrency patterns by hand for your different use-cases is nuts. I have lots of feelings here, most are summed up by https://gist.github.com/kachayev/21e7fe149bc5ae0bd878

Tulpe returns feel like they were bolted on to the language. If I want to write a function that does nothing more than double the return value of a function that might error (insert your own trivial manipulation here), I have to pull out the boilerplate error handling stanza when all I want to do is pass errors up the stack.

This is the 5% that I remembered off the top of my head years later. All in all, the design of go as a “simple” language just means that my code has to be more complex.
Someone had a similar thought https://twitter.com/real_human_vc?s=20
> the fact that someone had to have written those Unix programs in the first place

I think the key takeaway here is that it's better all around if somebody like Knuth spends their time and effort on those Unix programs - or, in general, the reusable blocks - and leaves putting them together in various ways to solve the different issues at hand to the less qualified.
I paid 20% federal (effective) and something like 6% state (effective).
Shout-out for "AutoSpotting", which transparently re-launches a regular On-Demand ASG as spot instances, and will fall back to regular instances:
https://github.com/AutoSpotting/AutoSpotting/

Combined with the fact that you can have an ASG with multiple instance types:
https://aws.amazon.com/blogs/aws/new-ec2-auto-scaling-groups...

Means that you can be reasonably certain you'll never run out of capacity unless AWS runs out of every single instance type you have requested, terminates your Spot instances, and you can't launch any more On-Demand ones.

(and even so, set a minimum percentage of On-Demand in AutoSpotting to ensure you maintain at least some capacity)
Lol document.write in a table in Netscape 2. Still remember my first experience with a buggy js implementation :-)

My favorite early js story is writing a “life cycle of stars” app in 4 hours in 1997 and getting a full high school semester worth of credit for it :-)
In Unix, C is THE API.
Training ML models usually doesn’t have the same uptime requirements as production systems. If your training goes down for a bit, it probably won’t make much difference to the underlying business, in most cases.

That’s why the author found it glaringly obvious that it should be brought in-house. It’s often both the most costly and most “in-housable” compute work involved in these companies.
Former NASA mathematician Katherine Johnson dies
Edited my comment. Didn’t notice that vendored got spelling corrected to censored :(
> what's the point of rewriting it in Rust

The fact that you don't have to write C and also that you can have different API semantics. E.g. you can pass user space code (say callbacks) to the kernel while maintaining safety.
I’m actually not a mobile dev, just deal with a bunch tech surrounding that space. Also, nothing against react native - used it for building quick things myself too - it’s just not something I’d pick to build say an Uber app, or something. And if you’re not building that level of an app, why bother? Web is enough.
Who is Scott Alexander?
I suspect doing that will break down in the case of large Spark shuffles though?
Why your company doesn’t have an internal Google
Very nice practical and modern textbook for OCaml. I were using it last year to teach this subject at my school. Here are my additional notes and exercises, if you are interested: https://a-nikolaev.github.io/fp/
Save Your Parents Marriage
I recommended Hack Wisdom who helped me hacked my dad's phone to know his cheating on my mom then,
i let him know that i knew his secret and he apologies that was the end of his cheating. I am excited that i could save their 15 years marriage. You can get in touch with him on wizardcyber 25 at gmail com or whatsapp +1 913 308 1303