shermanmccoy

So mobx is basically global state, and an efficient change tracking algo that decides which parts of the tree need to be re-rendered.

I've found using React context for state, and judicious usage of useMemo has been enough for me to be able to drop mobx or its kin, even on larger sized projects.

Libraries like mobx and redux implicitly promote a massive singleton state object. I think web applications are easier to maintain if we make every effort to minimise global state. If some component way down on the left hand side of the tree needs to get something to a component at say the top RHS of the tree, I will consider refactoring, rather than add another property to MassiveStateObject. Why? Because when you come back to look at MassiveStateObject in two years the implicit coupling between the two components above will not be clear.

A very childishly written article with no real insight. The real question in my mind is why on earth Bloomberg funded the writer's travel to Switzerland and Japan for this?

Helm is a mess of code, I'd suggest it probably has become unmaintainable. Ivy is my preferred completion plugin.

Cheers.

Any emacs users know of a linter that will tell me when I forget to await a coroutine?

Who would've thought that relying on a statistical model, whose many thousands of parameters are not understand, would lead to such an erratic end product?

It is very wide, those rotors protrude out dangerously, so it would not be able to land anywhere other than a specialised enclosure. Struggling to see the point, other than another attempt at realising some childish geekboy fantasy.

They would've spent multiples of that internally, just fumbling about trying to reproduce the vulnerability.

I presume Waymo has been knocking on every trucking company door in the phone book, trying to get some sort of pilot up, before opting down this rather costly path.

I think any reference to an authority is enough for people. Something like what you mention in your reply would be good to work in to the marketing material somewhere.

It's a good idea, kind of like a distributed gym. I think they need to invest more into convincing us that 7 minutes a day will do something for our health.

> HN readers like stories about real-world businesses,

Yes! This was more interesting to me than, for example, some dross about GPT3 generated poetry. Thank you.

This is the same argument that is often put forward in relation to accident rates for self driving vehicles. ML only needs to outperform humans.

The problem with this argument is it glosses over that fact that in the tail, where the ML is making a wrong decision, sometimes a catastrophic one, the behaviour of the ML algorithm is not well understood. How can we deploy something in such safety critical applications that we do not fully understand?

I see you used X. From what I remember when I looked at this years ago, X was really bad at highlighting dirty pixels. It couldn't tell you where your pixels had changed. So you had to flush the entire screen out over the network (vnc) every time something changed. This inefficiency made it unworkable in some cases.

Such an ignorant article, with the usual undercurrent of sycophantic nippohphilia. I'm so tired of sycophants on the internet pointing at some Japanese cultural 'thing' they have observed, in this case from reading someone else's blog, and presenting it to the world as though it is some unique discovery from the treasure trove of wonderful Japanese eccentricities.

This is not exclusive to Japan. Learning to write in also China, Hong Kong, Taiwan, Korea, and Thailand to begin with, stroke order matters. They carry over the same instruction technique when they teach English.

Thanks for the suggestion I will give this a try. I currently have Esc + <some key> bound to some of my most common actions. For me the 80/20 rule seems to apply to emacs shortcut keys, so making just a couple of them easier has a big impact.

With a simmering case of emacs chord key induced RSI I recently tried to make the switch to vim. The big thing I missed was magit, vim's port left me wanting, and the other tools just seemed like git cli embellishments. Just when I thought I was out, magit drew me back in.

Anyway, the screenshots from the OP make this project look like a very worthwhile undertaking. I can see why, perhaps frustratingly for the present project's author, this provoked a discussion on magit.

The recommendation algorithms seem to be just the most simplistic type of pigeon holing. Think Netflix, just because I watched a European political thriller last week, it is assumed I now want to watch this genre for eternity.

I'm surprised to hear this organisation is successfully doing ML speech to text. Is it running 100% of volume in production? Or is it more of a pilot type thing? I know of a French multinational bank that just tried for 2 years to get a ML speech transcription up and running, for transcribing conversations with customers, but due to unreliable results, recently put the project on ice. Their experience was much along the lines of everything discussed in this comment thread.

> Now, the biggest showstopper

Barely any stock market reaction this morning on the Taiwan exchange open (ticker: 2330:TT).

That's fine if you can control this configuration I suppose. But the escape hatch is there, so in my opinion TS doesn't go far enough.

Sure. However the any type lets the nulls in. And the any type is very convenient, perhaps even necessary to use in some situations. So then you are back to plain old js check blocks and ternaries littered everywhere. If you miss one, well, I don't need to remind anyone of the ubiquitous js console error which every js developer has burned into the back of her/his brain.

I use the Reason Language Server and eglot in emacs on a linux system and it is very snappy. Reason-cli gives you code formatting also.

For me a big strength is Reason's intolerance of null, this has eliminated a great number of bugs for me. Reason React ultimately forces you to think about every permutation of state your component might enter, and develop logic to handle that. JS/TS will never help you with that.

It was "banned" because they did not register the offering, not because the "people did not want the gold for themselves", in their childish analogy.

I was hoping for the pub from Shameless.

Representing meaning as a number, or more specifically a point or set in some vector space is fine. I'm not suggesting a more sophisticated concept of understanding than the status quo here, basically text in, a number/numbers out, which as I understand it is how most intent analysis works currently.

So meaning in this sense is very much quantifiable, yet how far along are we in parsing out even the most basic meanings? Can we build something which discriminates between "I'm moving in to <address>" and "I'm moving in on <date>", using the latest and greatest word embeddings? Not without some extra layers of external rules imposed on top. So the model does not 'understand', even in this limited scope of understanding.

Don't be fooled by the sentence recycling is all.

Boiling it all down, when prompted, these models just regurgitate a similar sentence to what is observed in the training data for loosely that same input, using some glorified curve fitting. This does not necessarily imply the model understands the meaning of what it is spitting out. So the uninitiated will be really impressed with this kind of toy.

The researchers here appear to have placed particular emphasis on cleaning up what the model is spitting out, but I think it's lipstick on a pig. The area begging for more research is parsing out the meaning of anything but the most simple sentence.

Why didn't he answer the first question in the Q&A session?

Some coding styles insist on tabs. I was referring to the third line of your configuration as quoted below.

; try not to use tab characters ever when formatting code (setq-default indent-tabs-mode nil)