Видео

are you ok grand pa 😢

this is the worst idea... everything is mixed into one heap... and this will add a lot of problems for everyone with color conversion... you need to understand what space and in what cases it is necessary to use... for this you need to at least first have a good understanding of base... for starters, it wouldn’t hurt to familiarize yourself with Munsell’s research... and others

Thank you

Extremely good talk. I learn so much and really only want to use OKLCH as a frontend dev now. I am just wondering what to do about supporting older versions of browsers, since wont recognize oklch() css function. Let's be real, many people just don't update their browser to latest. Is there some tool to help with that?

Thank you, very easy to understand.

Problem here you cannot use shared state because the remote app will not rerender. Solution will fail the moment u add something to the url for example want to have state in the url.

This was great presentation.

You get tightly coupled to a router and the next version introduces breaking changes then end up resorting to big bang upgrade/readjustment when you want to upgrade just one of them.

Lo mejor para matear un feriado!

Well, I enjoyed watching that. (Hi from Washington State, USA.)

ok

Talk is cheap

I've been trying to programmatically generate the palette for my text editor theme for a while now. HSL mostly works for dark backgrounds, but against light backgrounds my theme looks awful. Thanks to Oklch now I understand why and this talk shows it.

My name is Diane, and I am blind. I use voiceover all the time. There are so many Apps that are not accessible, and a lot of them deal with sound or music. Strange isn't it. We really really need people like you to go to developers like Korg or Yamaha. And make them realise what a quality of life they could give us. Also you've really got guts to be speaking to all those people when English is your second language. Absolutely brilliant!!! Keep up the good work.

The proposal "Misty" sounds a lot like JS talking to PHP with PHP using webworkers to reduce the workload of the server ..... Butt Ugly, but functional. O'course, you could have JS running on a server with webworkers ... Just image trying to debug that ... what could go wrong?

Excellent talk about the benefits of using device-independent color spaces.

Muy bueno. Gracias

Great talk! What is the tool you use for the visualisation?

Interesting talk!

wow thank you for 23 minutes of nothing useful

This is thought leadership!! 👏👏 Huge. I also have never found a to-do app that I like. I always end up using a text editor… probably because that’s about as malleable as is possible until now.

I think my workplace is mostly imperative mindset, I think it never occurred to most of designer's that how little irequired with declarative approach

speaks like a flash

Really great, thank you! Definitely this is why Notion and Obsidian are popular

BAhut sara

Hilarious

Max has extremely good knowledge on web development

I have faced challenges when pushing for accessibility but with the EU Accessibility Act I don't have to. Companies have to provide accessible services to their customers by 2025.

Describing the actor model as having been discovered at MIT in the early seventies seems somewhat imprecise. Presenting the right way to think about the actor model without referring to its inventor Carl Hewitt is ... well based on Mr Crockford's definition Hewitt might be 90 percent right on his actor definition.😂 Moreover, Reviewing language and paradigm history without any mention of Java and Scala/Akka and define the way forward for the industry at large might be incomplete.

man is a humble giant

Awesome video! Exactly what I was looking for. Do you have a repo with this code in it?

I edited this comment to be more "useful" instead of ranting only. I think the most useful is to realize the agents are basically what other people call components previously and there are real working solutions to this. Where this would have place? For example maybe removal of OOP and just adding this and modules would fit better. Isn't this just Dynamic dispatch, components, OSGi and some other things already easily done in Java lets say? To be honest even corba has elements of this already and countless systems implement it - just they are all far from the JS world so I guess they are unknown to JS native populations... Debugging this kind of system can be very hard. I was doing this shit in OSGi basically with added life cycles and it can grow into hell - yes it has some useful properties, but dangers as well.

It seems the next programming language has a lot of bureaucracy 😂😂 Liasons and Minions and no Hello World

I think the best paradigm depends on what the program is supposed to do. Generally Im in favour of a function OOP style like Scala, and F#. Of mainstream languages Swift is the one that comes closest, and also does have Actors built into the language itself.

When you haven't heard about Occam's Razor. No thanks.

It's highly evident that performance is of minor concern to this guy. If we listened to him, our already incredibly slow software would only get slower!

History tells us that for a language to become successful and popular it usually must 1) be familiar; be somewhat similar to existing language(s), 2) be somewhat easy to learn for beginners, 3) be quicker (or easier) to write new code, 4) have descent performance (usually). This is why LISP has taken so long for uptake, and why Haskell likely never will be mainstream. Ruby and Javascript have been the gateway drugs to making LISP and other functional languages more acceptable. Unfortunately, making a language with fewer flaws isn't necessarily a recipe for success.

@10:14 I'd rather think he's trolling... I mean, I'm sure he knows Smalltalk couldn't have solved the problems C++ solved (considering resource and efficiency contraints; not possibility). Still... Let the C++ mocking go on; it's part of the culture.

I somewhat agree about async await, but promises are way better than every library handling callbacks differently.

"There's an army of programmers maintaining that awful language" talking about C... We just going to pretend that we haven't wasted millions of engineering hours forcing JavaScript into every nook and cranny imaginable?

Very interesting video. It would be great if every language could use every other language as a client. Or just use the custome libraries from other languages. Not likely to happen, but it would be great is it were possible.

I don't know... Seems a lot more confusing than just the "regular" object-oriented way. But he may be right, who knows.

Thank you for providing a great example why I don't want to use the actor model.

Um, JavaScript can already do all of this. Sure, it would be nice to get complex communication and handshaking protocols down to a single keyword, and there's room for that in the market, but you import a library to do it, "just as good." We have MessagePorts, web workers, worker threads, websockets, and IPC for sending the messages. Agents that can do anything of substance are going to require credentials to use their resources, so you're going to have to pass some kind of credentials. I hope. I've always hated the nasty paradigm of implicitly trusting a webserver to do anything, then relying on junior PHP developers to secure the path between the user and the webserver. So do be smarter than that. If you have a long resource-intensive computation, you aren't blocking the main thread, unless you live back in 2008. We offload those, generally to workers but also to async processes if it's an I/O thing. We're always wary of the huge pure computation tasks tying things, but those are poor candidates for web browsers anyhow even if they weren't getting offloaded to a web worker. And I'm sorry you don't like promises. I have no problem figuring out precisely what's happening, and structuring my programs for simulated "concurrency" where possible. Promises in .then() chain structure are great for functional programming, and async/ await just cleans the hell out of everything. Callback hell is insanely worse, and I don't need parentheses 13 levels deep to know that I'm actually working with a callback, tyvm. And my favorite programming paradigm would be damn near impossible without async / await... to use async iterators. Yes please to a clean, consistent structure instead of using multiple event listener models and esoteric flow control commands. Compare a Node stream or a web stream (such as used by fetch), and there's no contest on which is easiest to implement. The biggest problem is actually the JSON format. It needs more than blobs and IDs. We have the structured clone algorithm, but most implementations keep this buried in the internal communications protocols instead of exposing it for general use. I have a pretty decent algorithm that can mimic most of it, but it's not a standard. We need dates, bigints, NaN, undefined, various binary structures, and some others to be serialized and passed through a channel. My browser will used structured clone through window messaging, and Node will use it with worker threads, but ya gotta cook your own to push it through a websocket.

This sounds terribly wasteful with a lot of unnecessary indirection. I wish people would take performance more seriously and stop wasting all of the wonderful resources on our modern machines.

So actors perform their tasks serially, so what happens if lots of clients want work doing? Is it ensured that we wont send to an actor already performing work because if not then that could lead to unpredictable latency.

How is this new? My curriculum had lessons about this 20 years ago?!

If we're calling the actor model a totally "new paradigm" since it was made in 1973, why couldn't we also introduce the totally "new conditional paradigm" called "KAIL Selectors", which were a new twist on conditionals starting in the early 1970s by David W Embley. I'm surprised that it took this long to get someone's attention too!

There “doesn’t look like what it’s doing” thing is very strange… firstly it implies we’re should all use assembly language for everything and secondly async/await is so much obviously better than callbacks 🤔

This sounds like temporal with go and grpc