essenmitsosse.de
Software Developer, Co-CTO, functional TypeScript Fanboy
69 posts
71 followers
129 following
Getting Started
Active Commenter
comment in response to
post
It stays on 100 for quite a while and then starts dropping RAPIDLY. like 10% in a few month.
comment in response to
post
Except when my app I made up of multiple parts that are deployed separately this doesn’t seem to be necessary or am I missing something?
comment in response to
post
Trisoloris trilogy aka the Remberence of earth past
Chinese hard sci-fi. And I mean HARD.
comment in response to
post
This should also work with any similar framework.
comment in response to
post
The good thing is, this is gradual and you can slowly make stuff more dynamic for example to extract blog posts. But I find it insane how much easier stuff becomes if you handle all the data in JavaScript and then have the site rendered vs having a database with WP crouching on it.
comment in response to
post
I recently migrated some WordPress sites to Next by having a scraper download the HTML and assets of the live site and then doing a lot of search and replace magic to convert it to a Next site in ~a day.
comment in response to
post
Do native speakers also struggle with this? I have no trouble with the German version of these but then again they are not abbreviations for Latin but for German.
comment in response to
post
Oh god I’ve been waiting for something like this for ages. And also have so many edge cases so curious to see how it’s implemented.
comment in response to
post
The worst offenders are those things where you need a plugin to TURN OFF a default Wordpress feature.
comment in response to
post
I also don’t see the plethora of WordPress plugins as a win. It’s a bad incentive to just throw together random stuff and hope it doesn’t make the whole thing to slow or unstable.
comment in response to
post
The price we where willing to pay for WordPress‘ somewhat decent backend was just way to high and I’m glad for every day I got rid of the Stockholm syndrome.
comment in response to
post
But that shouldn’t take away from the fact that the price you have to pay for WordPress backend is still astronomical in both infrastructure and development time.
comment in response to
post
I would take the argument „if you have a non-tech savvy customer who wants a WYSIWYG-editor to edit their content“. Building that with Next is admittedly a bit of work.
comment in response to
post
Have you actually build a site with NextJS? Have you ever build a Wordpress site that has some custom structure and isn’t just a blog? NextJS has a feature to just render out a static site, whereas Wordpress always needs a running database and a PHP server even if you want to do aggressive caching.
comment in response to
post
Given all the hoops you need to jump through to compile from TypeScript to JavaScript you kind of forget how straightforward it actually is. Except for enums.
comment in response to
post
The thing is, it’s just a dumb string sort. And I’m mad it’s correct 🥲
comment in response to
post
the fact that foo is either at the start or the end depending on wether or not both of them have an ending.
Discovered this because I automatically sort imports alphabetically with ESLint and just removed file endings in a project and was confused why a line changed place.
comment in response to
post
They and their work should neither be glorified nor normalized. This isn’t just some harmless cool new tech thingy without implications for society.
comment in response to
post
And as you’ve shown: those results are not even consistent between browser. Best case is you spend a lot of time writing code that is harder to debug only for it to be slower for most of your users.
comment in response to
post
Even if the performance difference would be an order of magnitude it wouldn’t really matter for almost all case. A function like this will probably be one of hundreds if not thousands that run in your code and optimizing one of them will rarely make a difference.
comment in response to
post
This is an on-site job, right?
comment in response to
post
That was a hard throwback to my time as an intern at a comic publisher doing preprint. 🤯
comment in response to
post
Imagine how much images could have been saved if we could have rotated images back then.
comment in response to
post
Yes. Now all we need is a way to also have this fixed for autocomplete so that all the possible numbers don’t spam the suggestions.
comment in response to
post
My point was about writing such functions myself. Which indeed can be hairy, even when possible. Also you might get types that are correct but very ugly and produce awful error messages (not sure if that applies to ts-pattern). I also think it’s valid to avoid adding libraries just to have TS work.
comment in response to
post
A good point. Didn’t see that one.
I generally consider it a valid approach to adjust your style so that it empowers the tools you have at your disposal instead of focusing to much on what the language might be able to express. It hurts at first but you get a lot of advantages out of that.
comment in response to
post
Hot take: TypeScript can replace a ton of unit tests.
But yes. I want to write code for the most stupid person possible. My future self.
comment in response to
post
I need people to understand how artistically superior this graphic style is to basically any major Tripple A game these days.
comment in response to
post
Selling TS on the promise that it is just some nice sugar on top of JS is misleading. It is its own language which happens to use the same runtime. There is the advantage of having a gradual migration path (which indeed is nice), but I wouldn't expect that path to be overly joyful.
comment in response to
post
Even if you try to avoid it, at some point you will have to write some functions with very nasty generic types. Isolating them as much as possible is a task, you don't need to do in JS. But I would expect a good TS code base to have a different runtime, then a good JS codebase.
comment in response to
post
Generally anything that is overly dynamic. Function overloads, prototype-based-patterns, changing objects after creation, dynamically parsing complex objects.
I find TypeScript becomes much more friendly, when you are more explicit and strict and throw away some of the things people enjoy about JS.
comment in response to
post
TypeScript should be more upfront about how its usefulness heavily depends on the style of your codebase.
Some valid JavaScript patterns feel painful in TypeScript. And vice versa.
comment in response to
post
I feel if you can appease to TypeScript it can become incredibly powerful. For me, it boosts productivity even before considering the guarantees it offers. But that might also be due the fact I struggle more with untyped code bases. Maybe others are better at just keeping things in their head.
comment in response to
post
NPM has some drawbacks, a lot of which eventually get fixed but it just hast the best overall support in different environments and usually just works out of the box in a lot of place like CI etc.
comment in response to
post
Usually NPM for the main setup. But most of the time i call scripts via bun for the simple reason that I don’t need to type „run“ and can just do stuff like „bun lint“
comment in response to
post
Was it package-json.lock or actual code?
comment in response to
post
Companies where able to bootstrap new products quickly before. What they struggled with is growing and scaling. AI might be slightly better at the bootstrap part and is much worse at the scaling part that eventually becomes the real problem anyway.
comment in response to
post
We also know how horrible year old code bases can get. We can only imagine the horrors of entirely AI generated code bases.
No one has seen a 10 year old AI code base. If any would ever get that far.
comment in response to
post
We need tools, frameworks and practices that make the relevant surface of a code base smaller and more elegant so they are either to fathom, not tools that cover the entire surface in a layer of incomprehensible darkness.
comment in response to
post
Never underestimate the value of a clean git history in which every commit can be trusted.
comment in response to
post
By “as often as possible,” I mean CI should run on every commit that reaches `main`.
The fact that there are often reasons why this is not feasible doesn’t mean those reasons shouldn’t be removed if possible.
comment in response to
post
Isn’t that what happened on Instagram in the beginning where all the text was in the images/videos and captions where just hashtags? Not sure what happened exactly but I assumed they footguned themself because this must have made making recommendations much harder.