skysight-inc/HackerNews huggingface dataset:
I don’t agree he makes good points at all. His arguments essentially come down to two things:

1. LiDAR is expensive - this makes sense from his perspective because he has already declared all Tesla cars on the road are capable of “full” self driving with their current hardware. If he walks back on his, he would have to retrofit a million cars.

2. Humans can drive with just vision, so why can’t computers? This is a naive argument because human vision isn’t just vision, it’s linked to a ridiculous intelligence in the form of human brain. And computers are nowhere close to replicating it.

If you want to read more on LiDAR’s importance, read some of Brad Templeton’s writings.

https://www.templetons.com/brad/robocars/cameras-lasers.html

https://www.forbes.com/sites/bradtempleton/2019/05/06/elon-m...
I also wanted to point out that Polar is Open Source.

https://github.com/burtonator/polar-bookshelf

If you'd like to look at the code.

We have a unique build environment so DM me on Discord if you want to build it... You just have to use lerna and our npm repo but should work well.
Study: Wildlife flock to backyards for food from people
The React team is working on some experiments that’s not quite what you’re describing but achieves the goal of sending way less code to the client. I can’t wait until tools like that are more standard.
If you understand each approach well enough they aren't context switches at all - they're just different tools for solving a similar problem. If anything, understanding each of them gives you a better understanding of the approach your team has converged on.
Ninja uses time stamps. See the “Comparison to Make” section in the linked manual.
"widely-used enterprise product" usually implies little forethought. Bonus points if it's communication/teleconferencing software.

There was this essay about this being an inevitable result, considering that large companies almost never take user feedback into consideration when selecting "enterprise software". Which is the reason most enterprise videoconfering software sucks.
They don't have enough funding. Next.js and Gatsby are in an entirely different weight class compared to Sapper.

https://sapper.svelte.dev/
Could be. Angular growth has stalled for the past year or so. Polymer is pretty much dead.

OTOH hand why would Google invest in a React-based solution? Google could start from scratch an create the next best thing if they wanted to. To me it's pretty clear the future is a compiler based approach like Svelte, with support for SSR, partial hydration, static generation, and dynamically loading smaller parts of a page (eg: AJAX + hydration). All with a kickass DX.
Reverse Income System
Am I missing the part of the analytics docs / announcement where they mention how to send that information to anywhere other than Vercel?

EDIT: described here in "web vitals" https://nextjs.org/docs/advanced-features/measuring-performa...
This is what the park looks like now: https://goo.gl/maps/aufMFdV1yBtQbACF6

Google Maps actually even has the Whiteread house itself, although that's just a photo inserted into a 2017 panorama: https://goo.gl/maps/3hVzRrs3PDbNXiwD7
See https://news.ycombinator.com/item?id=24820449 for original Peruvian coverage, including TVPE video and map reference.

See also https://news.ycombinator.com/item?id=24819730 for where this was on Hacker News last week.

Compare the BBC's coverage to the original Peruvian coverage and the Smithsonian's. The Smithsonian puts this in context of previous discoveries, that the BBC has no mention of. The BBC claims that the "platform would have provided a vantage point for visitors". In fact, the Mirador Natural has provided such a vantage point for some years, and there are plenty of tourist photographs of it on the WWW. The path mentioned was part of renovations. The access road now comes in from the south, as you can see in the video.

The Mirador Natural is some distance to the south of the Torre Mirador that is marked on on-line maps, which is actually the old observation tower, a new one (which you won't find on on-line maps) having been opened across the road from it in February 2020.

* https://andina.pe/agencia/noticia-lineas-nasca-nueva-torre-m...
Your employer is liable for state & local employment taxes and may also have to fulfill additional obligations like filing for a business license wherever employees are located. That's why they need to know.
Code+of+Conduct
My first thought was that Microsoft (or a subset of) probably determined any impact from an adversary taking advantage of these client side settings was fairly minimal (at least the messagePolicy values).

Then I remembered zoombombing is a thing and can be pretty disruptive.

It could also be an inherited problem from the days when teams was actually Skype for business.
Hi Chris! Thank you for your message! We are trying to be as fast as possible but maintain a quality level (we talk to each host before), so hope to add a couple of events more by the end of this month!

The activities shown in the webpage are real events that can be booked already. The price policy is determined by the hosts. But if you have hit your budget already I am sure that we could adapt to your needs! lmk @joalavedra
If anyone wants to know more about preventing interleaving, try using `make -O` or adding `GNUMAKEFLAGS += --output-sync` to the top of your Makefile.
That's cool, but why are you calculating CSS attributes dynamically at export time instead of just writing a stylesheet and putting that in an export theme? Separating presentation from content, etc.
IE11 is an unsecure browser and doesn't even support numerous HTML5 security features. Any business that still relies on IE11 is asking to be hacked, no more, no less, because it also means that these businesses are still running older versions of Windows.

Now IE11 isn't even an excuse because $current_year ES version can be transpiled to older ES versions.
Radars already go 100m+.To avoid a front collision pretty much all these systems use radar, not lidar. Next generation radars are already doing 300m+.
Yes... if you delete documents it those won't count against your quota.

We've also tried to make it pretty cheap so if you have a huge repo it won't be super expensive. It also won't bloat your local computer so if you have a large repository most of that data will be on the cloud.
I heard somebody say "Haskell people tend to write libraries, Rust people commandline tools". Pandoc is the excpetion that proves the rule ;-)
The React team is or was reportedly working on "progressive hydration" which sounds like what you're talking about.

This tweet from React core team member Dan Abramov in December 2018: https://twitter.com/dan_abramov/status/1079352276433715200
Are you sure about that note? I have one phone that is some years older than Twitter and it supports long SMS transparently.
Most of the websites I write these days don’t have a build step for development, only for production. Modern browsers (and modern node) support ES modules, so there is no need to build anything until you ship to a legacy browser.

The only pain point of not building during development is when I need to pull in a third party dependency (since node and browsers pull from different sources; and import-maps is not is still not a standard), but if your are not using any third party dependencies, you should be fine.
Seems a bit of both. They put the self-hosting docs on Vercel.com (https://vercel.com/docs/next.js/analytics), as it requires setting up a project and paying for it on Vercel.

Cloudflare offers the same thing for free.
So I suggest trying vanilla Postgres RDS, which doesn't have IO fees, but is still managed.

Also, if you're doing such heavy IO, you might want to also look at I3en instances, which have fantastic IO using local storage.
Red Dead Redemption Fan Art: Photogrammetry Workflow
February 2021: Next.js has been discontinued.
You'll soon be able to go live for four hours on Instagram
Google Suppresses Breitbart News in Search – Even with Exact Headline
OberonScript: a safe scripting language and runtime for web apps (2007)
This is odd (public/scripts/TodoList.js):

el.innerHTML = [
'<div class="items"></div>',
'<div class="todo-item-input"></div>',
].join('\n');

I wonder why aren't they using `DOM.createElement` instead of innerHTML since they will query for those nodes later anyway.
I deliberately didn't link because jwz does not like hackernews linking to his site.
150 separate HTTP requests on startup? That seems quite a lot. I'd guess its smth multiplied by the number of teams you have?
And... Sapper is dead btw.

Rich said it recently in a video. The Svelte team is working on the next big thing combining Svelte with Snowpack. The project is called SvelteKit.

https://www.youtube.com/watch?v=qSfdtmcZ4d0
Yeah I think it's both more effective and cheaper to have dual/quad socket systems with 1 "normal" CPU and the rest filled with FPGAs without CPU cores, just to max out on the raw crunching ability. The PCIe block on the FPGA chips could be flexible enough to (re-?)wire directly into the programmable logic, maybe even reconfigurable to other protocols (e.g. 100GE). Also in "normal" NUMA fashion each FPGA would have the memory channels associated with that socket (presumably through the interconnect as if it were a CPU, so the CPU can access it too.)

I'm just looking at this from a logical chain of "who needs FPGAs in their computers?" => "cases with loooots of specific data crunching" => "want a controlling/driving CPU for the complicated parts, but then just concentrate as much FPGA in as possible." => Multi-socket with 1 CPU & rest FPGAs.

(There currently is no commodity Quad-socket SP3 mainboard, not sure if this is a design limitation or just no one made one yet? I'd still say the approach works great with only 2 sockets.)
It sounds like a big deal. What a tempting idea. And a colleague was mildly annoyed with me for how unimpressed I seemed.

But you have to understand, the use cases you mention are shallow and limited. The heart of GPT, the fine-tuning, is gone. And it looks like even OpenAI gave up on letting users fine-tune, because it means they essentially do build an entirely new, expensive model for each use case.

I wanted to make an HN Simulator, the way that https://www.reddit.com/r/SubSimulatorGPT2/ works. But that's far beyond the capabilities of metalearning (the idea that you describe).
You aren't getting 3-5% cash back unless you are using tons of different cards for different types of purchases and are also keeping within limits.

There used to be a 3% cashback on everything card with no limit. Now 2% is the best and difficult for most people to get.

You can get 5% credit back with an Amazon Prime card but only on Amazon.

Most other 3% or more back are either limited to a niche category and/or capped. (Like 6% back on groceries, but only for the first $6k).
>I wonder how long it will be before the company changes its name as a result of the bad reputation from this incident.

Never. People and organizations that purchase that kind of software just don't give a fuck.
The combination of removing ANGLE (guaranteed baseline GL support on Windows) with it not being possible to use the new rendering stuff for APIs other than GL if you aren't using Qt Quick seems potentially problematic? (I have no experience with these tools though.)
Yeah and it's first citizen too, it was upgraded from needing a @zeit/plugin to working from scratch in a new nextjs project.

Just add a pages/index.tsx, and run yarn dev, and next will create a default sensible tsconfig.json file for you and run the project!
translation: it's a bunch of frat bros
> for filename in things_to_convert:

Undeclared variables and random indentation levels. Is it safe to assume these examples are abridged? Or is it a case of magic?
As someone who only really built websites using jQuery / custom vanilla js and good ole CSS2, this stuff feels completely alien to me
congratulations on missing the point of the whole thread.

Also, for having biases, people are actually getting called evil (racist, nazi, bigot, etc) every day, and are expected to apologize/be fired/read more sacred texts/participate in group exorcisms/etc
Relevant documentary: https://www.youtube.com/watch?v=lJKBvXsq2Y8
PM Suga says Japan will attain zero-emissions, carbon neutral society by 2050
They've been talking about it for years alongside with SSR streaming. Nothing concrete so far.
As another comment said, this is pretty basic stuff. Though I am not surprised. The Teams client is pretty bad. It's slow and clunky. It tries to do way too much while succeeding at very few things.

The desktop client chat _still_ doesn't have a "reply to message" feature, while the mobile client has had it for, what, more than a year? This is a feature that _should_ cost a competent engineer no more than what, a week? to implement. The team should take a note out of Discord's or Telegram's book to improve the chat experience. It's really very bad.

In the meantime the latest noticeable additions were mostly fluff like extra ways to show webcam stream backgrounds, and a "cinema-like" webcam-view.

It's interesting that the same company can produce both Teams, being pretty bad, and VS Code, being very good.
PyTorch 1.7 Released with CUDA 11, New APIs for FFTs, Win Distributed Training
In the early days of Exchange I was curious what would happen if I setup a rule for two clients to just reroute emails to each other back and forth.

So a buddy of mine and I tried it. The rerouting was done (as far as we could tell) client side and it seemed there was no inherent server side method of detecting such scenario.

Company email for a few thousand folks went down after the two clients took off doing their thing for a short while.

IIRC the client wasn't immediately inclined to forward other forwarded emails (again enforced on the client) but an easily crafted rule would bypass that easily.

At the time I was surprised there wasn't any automatic prevention of such things, as my career has gone on, I just assume such things aren't there ;)
I've noticed from pair programming that the person navigating with a mouse is far less able to read and interpret their surroundings or pick up typos while typing, than an observer that simply has to watch what the other person is doing.

Like when clicking on a file in a directory you just entered and looking for the file, the observer can literally locate and point to the file for the mouse user 5-10x faster than the mouse operator.

The observer seems to interpret the information that results from the directory listing faster than the person who just did the double-click to enter the directory because they don't have the muscle coordination context switch and can immediately move to interpreting the results.

It's probably because mouse manipulation uses brain infrastructure that is more recently evolved, but observe-react is a lot earlier in the brain processing pipeline evolutionarily, and a lot more refined/involved.
Receptor dysfunction in AD brains has been an active topic of research for decades, and most of the drugs approved for treating AD (NMDA antagonists, cholinesterase inhibitors) modulate neuronal activity.
People made crop circles with little more than planks of wood, bits of string and rope, and stepladders, remember.
Any idea what Apple's LIDAR specs are? Just saying that if the sample rate is only supposed to be good enough for auto-focusing a camera every second within a 10-20 degree FOV on-center, then there's still a deal of improvement needed before they can be used for self-driving cars. I think the tech will get there eventually, but this is an area where the sensor specs become really important.
In Mexico it's a soda drink. Very popular for mixing with alcohol.

http://grupopenafiel.com.mx/bebida/squirt/
Qt Quick has historically been a toolkit for building custom look'n'feels, so essentially every Quick project needs a UI designer. For projects where custom LAF is important (e.g. all those car infotainment systems), this is not a problem and expected/accounted for. But for "general purpose" desktop apps - well...
Tablet oriented UI, installing custom CA certs don't work, keyboard shortcuts are all gone.
Simple Faraday Cage for Your Phone
Which implementation of BLAS/LAPACK? Because if it's the ref. implementation then it's not that impressive, the performance of that is very poor.
Not OP, but in my reading of your case study, you still made a framework. Instead of having a code-based framework, where the methods and classes enforce how you implement your system - you created a convention-based framework (use a specific CSS naming technique, model your JS on this template, etc.).
I've only worked on one project (https://www.dpdk.org/) using meson+ninja. Overall it seems to be an improvement, barring the make idiosyncrasies that needs to be forgotten.

That being said, if the project had used make properly from the beginning (i.e. avoid recursive calls), it would not have been plagued by such latency for incremental builds. But then, make should not have made it so easy to fall for such mistake.

I'm still not a fan of having two steps (meson + ninja), but I guess it's always needed for multi-platform projects.

I'm wondering if there is a make rewrite project that tried to make the recursive make antipattern less painful? Maybe trying to recognize sub-calls and avoid creating a sub-process? I guess it would take creating a small internal shell with only make as a builtin command...
"nuclear" implies indiscrimiately devastating (lots of collateral damage), not just out of proportion, so losing a job, while painful in the moment, isn't a "nuclear option" for this sort of sexual malice that instills real doubt and insecurity in victims and divides employees and customers otherwise. a lawsuit and an arrest might be closer to that extreme. or at the extreme, a lynching (in no way advocating that of course).

hyperbole has the exact extremist effect you're railing against, which is indeed needless.

with that said, a demotion, an unpaid furlough, or pay cut may be part of a more reasonable consequence, giving the offenders a chance to reflect and grow (and eventually return to their prior status), rather than throwing them into a potentially negative cycle.
No. Lol. Cooling anything other than the controller is pointless. You don’t get throttling from nand. I have the gigabyte x570 elite. That nvme cover does nothing. And unless you’re benchmarking the nvme I highly doubt you’re going to heat up the controller enough to notice it. So yup. I agree. You’re wrong. Let’s move on.
God I hope not. Mass methane release is an extinction level danger, and I believe there is geological research to back that up.
Just so you know, for GPT-3, Microsoft is going to be the exclusive licensee of the API: https://blogs.microsoft.com/blog/2020/09/22/microsoft-teams-...
Posture assessment is often built into modern VPN clients. The actual procedure varies by organization and can sometimes be updated by pushing new validation procedures to the client. It's unlikely to be as simple as "run this file on disk (which an attacker could trivially replace) and check the exit code."
See https://news.ycombinator.com/item?id=24909094 in this very discussion.
> really I can't understand the thought that goes through some of these guys' heads that makes them think it's OK to do this.

Well, note that in this case they didn't get fired. So... that might make them think it's ok to do this.
"code of the compiler is available... for personal, non-commercial and non-governmental use."
Did it ever have a single meaning? Every company I've been through had a different definition of what "AI engineering" should be
One of the best parts: Time will tell how effective each campaign manages to turn data, analytics, ads, and fundraising dollars into actual votes on Election Day
As much as I agree with you and want one for myself too, I doubt that this market segment is interesting to AMD at all. The kinds of workloads that warrant going FPGA are the kind of workloads where you just give your devs a bunch of high-priced development systems. Those would likely be close to identical to the production boxes, just with more debug pieces plugged in.
I think its great. IELR is a straightforward optimization that just makes sense to use when building an LR family parser.

You can think of LALR(1) as just taking an LR(1) state graph and merging together nodes that are compatible (in that they are essentially the same parsing state, but differ in which "lookahead" tokens are valid). A grammar is consider to be LALR(1) if combining states in this way still results in a correct parser.

IELR, which is derived from David Pager's PGM and Lane Tracing "Minimal LR" techniques from the 1970s, applies a stricter compatibility test for nodes. This check usually allows a large majority of merges while rejecting the ones that will lead to parsing errors. In this way, a more sophisticated grammar, all the way up to LR(1) can still be processed correctly using a table size much closer to what you get with LALR.

You essentially get the best of both worlds and its tragic that this fairly simple technique is so obscure. I believe the reason for the obscurity of these techniques is that Pager's PGM and lane tracing papers are extremely terse, somewhat confusing, and lacking in sufficient detail in certain areas. For example, the PGM paper on p.256 crucially notes that successors may need to be "regenerated as a distinct state" without further explanation. (Until his protege Chen provided some pseudo-code 34 years later in his dissertation of 2009. BTW, I have verified that the Wisent and Menhir parsers and others implement PGM correctly, if anyone is looking for actual details.)

Note that there is some additional time and complexity required to detect conflicts and regenerate/split nodes and so the benefits or IELR are not entirely free.

More obscurely, it should be noted that IELR suffers the same problem as LALR in that combining states can introduce conflicts between tokens when context aware lexing [Nawrocki 1991] is being utilized. (BTW, Tree Sitter uses context aware lexing but its not very common otherwise - yacc/bison doesn't AFAIK). Suddenly tokens are eligible for matching alongside other tokens that normally would not be matched together. Unless your tokens are globally conflict-free or you've got a priority scheme that always resolves conflicts properly (but then you wouldn't need context-aware-lexing would you?), you'll start matching tokens that shouldn't be matched in a particular parsing state. There are ways to avoid those conflics as well (see PSLR - also from IELR author Joel Denny) but it is a lot more work. Even if you avoid conflicts, invalid content can match tokens that shouldn't be matched which complicates error reporting because you get a confusing parse error instead of a correct tokenization error. So this is one case where the full LR(1) may be preferred over IELR.

But I can't think of a convincing argument for preferring LALR over IELR.
Deleting your Facebook account forfeits Oculus VR games you already paid for
There is light at the end of the SPA tunnel :)