oof. i knew instantly what the problem was and realised these people have no clue about how video even works. yet another vibe coded AI startup.

If that makes you cringe, I cannot even begin to imagine what this https://tinygo.org will do to you.

the blog touches more on the management side rather than development so the term engineer seems misused.

i encountered this topic many times in my life and after many years i can safely say that what makes an engineer being considered a senior is simply a talent, or learnt skill, of problem-solving without outside input. meaning, a senior engineer will find a way to get things done, just like special military guys do, without reliance on other people(as in, there is no safety net of skilled colleague who can help when needed or answer complicated or deeply technological questions). one is one one's own, so to speak. it is the same mindset, or rather attitude of not giving up and ploughing trough a problem until solution is achieved.

it's not hard to make something without funding, even by yourself, as long as you have the time and skill. but problem of the internet of today is saturation. you can have the best service or tool, much better than the number one on the market, but if you have no cash to burn on ads, you won't get anywhere.

i have not read the history of this project but i would consider this as pure luck and nothing more(sadly). nothing wrong with that, but understand that this is a unicorn(not as in 1B company but as someone who was able to make profit).

---

Ah, here it is:

> DatoCMS started in 2015 as an internal tool for our italian web agency.

Yeah, almost every agency used to have its own system back then, before drupal, wordpress and other CMSs were more popular.

Starting in 2015 it makes more sense why a big win for them this year was getting typescript setup.

FYI, IDEs and editors too don't use "textarea". Contenteditable essentially makes the web browser work like editor does.

Contenteditable plus the CSS Custom Highlight API (which highlights ranges instead of elements) might indeed allow for a good solution. But I have not yet seen an editor that does that.

I built a prototype that does work. https://hypervariety.com/ScriptHighlighter/

There are no such blogs. Usually companies, or individuals, will write these after they implement some feature into their products. Which makes them inherently little pieces of information scattered all over the internet and there is no one blog that is just about this.

That’s true. This kind of writing usually shows up as post-implementation retrospectives, so it’s inherently fragmented.

I’m trying to surface and study those scattered examples—especially the ones that explain why decisions were made, not just what was built.

Even if you could add canonical link into the header, you cannot have canonical link represent content on another domain. So no, there is nothing do be done in this regard(even if anchor itself would support rel=canonical).

I would just add link to the top of the text pointing to the new location with a note and leave it be.

Oauth's PKCE verifies the continuity of the flow as it is essentially a saga(multi-step process). For example you can initiate oauth access grant request multiple times with the same data, but PKCE ensures that each of those initiations can be individually identified. Do not confuse PKCE with state field, which is for XSS and has no obfuscation.

Just to be clear, the PKCE secret can be the same for each initiation, but in the end its goal is to ensure that the first request matches with the last one. And yes, there is "plain" PKCE method but that is just for testing. SHA256 is the default one used to obfuscate the secret.

You can hardly beat the first one to market due to momentum, time, data, user base ...

LinkedIn flipped the job hunting from job offers DB to CVs DB with networking aspect and added jobs and more social aspect later.

On the other hand, the web is insanely oversaturated and in the end everything turns to steaming pile of shit because of it. so even if something new came, it too would suck sooner or later.

Load and related expressions would be appropriate. Import implies the data is being put into the code, just like the plugins/modules.