HN user

silok

23 karma
Posts1
Comments28
View on HN

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.

[dead] 1 year ago

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

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.

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.

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

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!

Ditch That Else 3 years ago

The guard statement in swift is pretty much designed for this pattern, and it works well imo.

It is a pretty common phenomenon that parents continue to live in their single family home long after all the children has moved out. At least in Sweden this is definitely the case. Not really a lack of single family homes, but too much friction for people to move to a more fitting home.

I think it looks pretty promising, as long as the deployment setup is not only configurable via the UI, but also can be specified decoratively with code and hierarchical data (eg json).

IaC is a really powerful concept, and system initiative does not need to be in conflict with that paradigm, just another layer of abstraction that still allows IaC.

The main issue is how to combining UI state + and manual state.

The worst thing you can do imo, is to use a common representation, eg the UI would try and edit your manually written declarations. That is just a recipe for disaster.

The answer to this type of mixed editing is a layer approach, eg what is being done in the USD format (https://openusd.org/release/index.html)

Each authoring "instance" has full control of its layer, and composition semantics define how the layers compose to the final declarative structure.

Uh, dude, the first iPod was amazing. Lots of storage and firewire made transfers ridiculously fast, but yeah the target market was probably people who already had a modern Mac.

Also the physical wheel was amazingly good UX, and very responsive.

Honestly, how often do you bang your head hard into a wall/floor? Sure, I'm a tall guy, roughly 200cm, and I sometimes bang my head in a overhead doorstock. But that is typically some old cottage or similar, where I would probably not bring a XR headset anyway.

Isn't that just due to "lazyness", rather than an explicit design choice? I mean just doing char based comparisons, which is the easiest solution, will give the separation of uppercase and lowercase (at least for ascii and similar encodings).

Nim 1.6.2 5 years ago

There is a difference between variables and types.

For instance, in C#, with capital-case convention for variables, it is common to give a variable the same name as the type.

eg `public Player Player;`