bartq

Other thing I'm worried about: how to retract facts from ML model? I guess it's impossible, you need to retrain from scratch with part X removed from training set. Or... people could invent layered ML models similar to docker - each layer would be marked what data it was trained with. Then at least you'd have some cache of trained model to re-use in next training session. Nasty stuff.

Probably psychological: major version change equals in people's minds to some marketing event/website announcement, developers/users meeting etc. Which is not how semver was designed. For this kind of event developers should reserve subname, like macOS Mojave, Monterey etc.

Yes, until there is a breakthrough and the game starts overs.

My friend, in my opinion "cloud" is a temporary trend, soon enough whole AWS/Google Cloud will fit into your pocket because of Moore's law and miniaturization of computers. Cloud is a money pomp and it's managed by admins and marketing people mainly, not by real computer scientists which conduct research and draw conclusions from the history.

I can recommend you to watch YouTube videos and watch people like Alan Kay (watch all the videos), Hal Abelson, Jerry Sussman and others pioneers of our industry. You should quickly notice that what we have now is a local maximum of some trends and much much more is waiting to be (re)discovered.

Hint: AWS and K8s are poor attempts to create real Object Oriented system. There will be much more like them in the future, but of a higher quality and based on some real rules, not accidental connections with HTTP messages.

1. With this approach of sending "only the small JS chunk needed for interactivity" aren't we going to end up with the situation where chunks A and B need common part C? And what if C needs D etc. There should be provided a dynamic modules loader. Is it implemented in all those hydration based frameworks?

2. How is solved the situation when <button> is delivered to the user, but "onClick" action is not because network failed?

I can add my 2 cents to the Smalltalk discussion as I've been watching just recently many of the Alan Kay's videos on the YouTube.

I can summarize Smalltalk thing this way: existing Smalltalk implementations (Squeak, Pharo etc.) are not something we should use in real world, they are just proofs of concept and food for thought. Real Smalltalk-like/Object oriented systems were bespoke written for specific machine and specific customer. Current day examples of OO (object oriented) systems really are... the Internet with all of its nodes, operating systems UI windowing systems to some degree (although very crippled and simple), maybe something like kubernetes, but again, it's very crippled and awkward. The ultimate goal is to create an environment, where there can exist objects (let's say processes/agents), which talk to the environment and other objects using messages. On top of all them you should be able to create full programming language which would allow you to compose/iterate/send messages to objects in any way you want, creating as many levels of abstractions as you wish, maybe creating new wrapper objects keeping some other objects inside etc. The programming language itself also should be the subject of real object orientation, for example the debugger or running program should be an object reacting to messages like "stop", "resume" etc. Languages like Rust/Go/JS should be used only to implement internals of some object and react to incoming messages in its narrow area when managing memory, data structures and IO. This is partially true today, we use OS to send messages/pipe sockets etc to the objects/processes. Sending messages should ignore the physical location of the object, just like the Internet does.

Thinking this way, the glue code we write today should disappear in 99%, we should be able to start thinking in higher abstractions, about running processes, computations in time and space, how they relate to each other, make queries to the processes, create interceptors etc. This is that I see when Alan Kay says the computer revolution haven't happened yet and we're still dealing with bag of bad ideas from 60s and 70s. Just packaged in nicer clothes, because we have faster computers and better screens.

We should start thinking longer term and not focus on immediate money as quickly as you see some results, because that's running in circles and real wealth is not created.

If this works, it means pretty soon will work sending whole application window from iPad to macOS and vice versa inside some "iEnvelope" Swift wrapper which will allow much higher interoperability. Will be exciting to see it, but at the same time it's disappointing how slow the progress of improving end user OS UIs is.

Add your comment as [After 10yrs update] section in your post :)

That's one of the best things I've read recently.

This is also the kind of articles the HN should be used for.

What the author wrote just works and it transcends technology world. Works in almost all contexts.

You can tell how Gunicorn is old by looking at example showing only 4 workers :)

A bit of offtopic: Mini LED screens honestly are disappointing for me to some degree. The blooming is a real thing and I can see it every time there is bright content on dark background. I do accept it because there is no other better option really. I can see this blooming both on MacBook Pro 16 M1 Max and on iPad Pro 12.9. It looks especially bad when bright contents moves slowly, you can see those backlight zones edges and you can observe one zone gets turned off and other on. Awful.

I also own Gigabyte AERO 15 OLED laptop and I must admit I prefer this screen over Apple's. White text on black looks amazing and to be honest feels a bit magical, like a thing floating in the air, especially if I look on this screen in a dark room. Code, terminal content looks amazing. It's only 60Hz though, but for mostly static coding 60Hz is enough. Ubuntu works really well, so I don't have to deal with Windows for programming work if I don't have to.

I'm tempted to buy LG OLED 27EP950, it's expensive, but honestly I'd pay those money to reproduce Gigabyte AERO 15 OLED experience on 27 screen. But I know it won't happen, because LG screen will have worse pixel density, it's only 4K. It should be 5K at least, or even 5.5K or even 6K.

When cross platform windowed WebGPU on Deno? It would be interesting for many kinds of apps.

> all the best articles that I've read and shared in the past have been been things that the author would probably have felt compelled to write even if no one bothered read their work

I've felt compelled to write this question on HN. Even if I don't draw anything for me, maybe someone else will. Additionally, remembering I asked this question and didn't get inspiring answer, I might finally be compelled to write my own thing without any other questions. You never know.

And if we already do meta talk: 1. Every rule has an exception. 2. Always do most exciting thing, today it's asking a question, tomorrow it's writing an article. Rule 1 works for points 1 and 2. And also works for your impressions about best articles. :)

Feels like a good move. How else could framework be developed than implementing some requirements. Vercel should provide lots of them. What else can be added to Svelte btw? It looks like a finished project already. People can only invent in Svelte area if browser standards move forward, right? Otherwise Svelte can only be used to support needs of some platform.

That's definitely the same idea: http://metaes.org/docs-metaes.html.

This will work once we have keycaps with e-ink or similar technology and this will be super cheap for everyone. Then we all will have keyboards with infinite number of characters and new chapter of typing will begin.

Another similar tool: https://www.youtube.com/watch?v=fQvWMoOjmQk

13 inch Pro has brighter screen I think, and that is noticable.

  Remember what I said earlier: UI is a functional representation of state.

Hmm, in React, true. But in general case it's not true. I expect new way of (better) two way bingings to emerge.

I think we eventually will be able to evaluate JS in context of types and return whatever we want even asynchronously. Now we have some combinators given by TS authors which allow us to compose some limited set of computations. I don't know how Java does it, but I hope TS will do it better :-)

That's pretty neat. What I really want is this:

  function fn(query:string){
    const stuff = // do some stuff with `query` variable
    return createType(stuff);
  }

  type MyType = FromJS<fn("SELECT id, name AS nom FROM things WHERE active = true")>;

This way we could compute types on the fly with JavaScript instead of creating monstrous types in TypeScript types system.

It really reminds me of Jai programming language by Jonathan Blow. Just downloaded and started testing it, looks promising! Is its main use case for now the games development?

Price is not objection, but could be always cheaper, right? ;). Awful parts are: - fans are very loud under CPU load, - keyboard heats up very fast, - touchbar freezes sometimes, because it's controlled by main CPU I guess, that's not acceptable as an input device, - no esc key (I know it is solved in lastes MacBook 16), - key travel is too small (again, solved in MacBook 16).

Nothing wrong with your situation, you're just experimenting and learning. Keep doing what interests you most, you'll eventually settle on something for longer period of time.

Title should be "If you don't work on software product, you’re not writing code, you’re solving business problems with code".

Those kinds of laptops/tablets are great for one reason: no heating components under keyboard. I hate "heated keyboards". I hope Apple will at some point allow to install macOS on iPads. Seems like it's possible, until that moment it'll be only consumption/sensors input device which is a shame. Unfortunately not a programmer machine.

I don't really know what Gatsby is good at because I've never been target customer of it. But judging on website and docs I think its power lies in simplicity: people want to get shit together and call a day. This tool allows that. It probably won't live long, but that's not a problem, right? Most websites built with it are short lived: promotion www, sales, register forms etc.

Yeah, FB releases libraries only to avoid walled garden situation when they can't hire new people because they're not pre trained or they don't want to use closed and internal only technologies. Remember React licensing problems? These days most of frontend jobs are actually React jobs, which i don't like, I like vanilla web.

Over the time I began more and more appreciate Microsoft's "boringness" (which is debatable itself) because their tools are real products, not marketing tools for developers. What matters more for serious project is tools quality, not few hot CS ideas loosely implemented on a knee.

Question: where is it used today?

I'd really like to see Flash reborn on WASM. WASM is a standard, so there will be no problems known to software produced and distributed by a private business (Macromedia/Adobe), problems like closed format, resources access control etc.