I frequently found myself needing to convert video files and everything is either paid, needs login, full of ads, or uploads your files. So I built my own tool that has none of that.
Yes, exactly why I built this. Works surprisingly well for my use case so far which is cutting ~300MB mov screen recordings down to size and converting them to mp4. That said, converting large videos to GIFs will almost certainly run out of memory.
The ease of getting things set up quickly and usually for free when starting up is very tempting. Later, migration is usually considered risky and not worth it because of maintenance overhead - which I would argue has become very easy.
I am working on https://spatialsheets.com Think geodata formulas + excel. Mostly for my own use just to quickly debug geodata. Used to heavily use geojson.io for it but it is not very good at handling large datasets and couldn't enrich data so I started working on this thing.
I feel like if you treat temporary variables as documentation they feel less icky. All these examples with the pipeline operator cause way more mental overhead than reading temporary variable names.
This looks like some visual artist was given a task to design the UI. Visually interesting but completely disregards UI research and usability standards.
3. So when that dependency gets removed by npm uninstall how should that comment be handled? You know that in business we just would end up with a bunch of dead comments in the package.json - is that really a better alternative than just using Ctrl+f to find where the dependency is used?
I do not remember the time it has ever crashed - and I am quite sensitive to software not working well. I can complain about the strange UI choices but not about the stability. Running this on latest Apple TV 4K
Who is the competition besides Algolia? Last I checked most of the competition is either very expensive or very feature limited compared to Elastic/Solr.
Thanks for the explanation. I guess the overhead does make sense at a certain scale. The unfortunate thing is that articles like this always end up inspiring some bored engineer/CTO to redesign everything so it is "webscale" like Netflix and blow the mid/small-sized companies' Christmas bonus on AWS bills.