silok

Explained at the end of the article:

After a full month of coordinated, decentralised action, the number of articles about Mr. Woodard was reduced from 335 articles to 20. A full decade of dedicated self-promotion by an individual network has been undone in only a few weeks by our community.

Perfect is a strong statement, I do not see that description on the github page?

I think this is a valid point, the tesla is not necessarily worse than humans. This whole test setup is built around the advantages of lidar which of course will detect the obstacle.

Human driving through painted wall:

https://www.youtube.com/watch?v=0NRerHC7g-0

Also, bruno has a custom declarative API request DSL that is suitable for text-based editing, complementing the usage in the GUI application.

https://docs.usebruno.com/bru-lang/overview

With autonomy you do not need a one-fit-all vehicle that support many different use cases.

Instead you have access to a fleet of specialized vehicles that are optimized for different tasks. Eg many trips might still be with only one or two passangers, and then a small two seater makes a lot of sense. If you need larger capacity you simple order a ride from a suitable vehicle class.

People interested in this should also make sure to checkout Hylo, https://www.hylo-lang.org

There are several presentations on the design and mechanisms. Eg

- https://www.youtube.com/watch?v=ws-Z8xKbP4w (Val: A Safe Language to Interoperate with C++ - Dimitri Racordon - CppCon 2022)

- https://www.youtube.com/watch?v=oFupPFniD9s ([IWACO23] Borrow checking Hylo)

This is very cool!

A bit disappointing that this does not get more attention on HN. Using WASM as a sandboxed embedded compute environment has so many use cases outside the browser.

For example extensions/plugins in code editors is another very interesting use case.

This is definitely some creepy behaviour by the tech lead, but how is it sexual assault? This just deflates the meaning of sexual assault to mean any kind of "uncomfortable assault"?

Also because xitter provides a broader discussion platform and reach compared to only HN (even though I highly appreciate the HN content). But yeah, the xitter post should preferably also contain that url to the source.

The topic of programming languages in game development, and realtime interactive environments is such an unsolved issue that needs a lot of attention.

There are huge problems eg with both the Unity C# approach as well as Unreal C++.

The swift approach is very interesting indeed, and Miguel de Icaza as the author gives additional reason to follow this effort.

Additionally the Verse project from Unreal is extremely interesting imo, and has much wider scope/implications.

https://www.youtube.com/watch?v=OJv8rFap0Nw

It feels weird to not include some sort of ML inference tasks when benchmarking modern compute hardware. The GPU capabilities are a major factor of the M3 upgrade it seems?

But that is basically the core value proposition of mojo. You don’t need to drop down into another language to do low level, high performance kernels, you can do it all in mojo. Scalable in terms of target domains, (somewhat similar in that regard to swift).

Overall very informative. Really like the comparison with the Dart analytics protocol and the Jetbrains protocol. I think the comments on state synchronization with subscription based feature providers sounds very promising.

Hopefully LSP specification can evolve over time and incorporate some of these ideas!