As usual, it depends. I know some friends that have profitable websites because they run on a private server and they handcrafted everything. If they had to use cloud services for serving stuff, host the db, provide search and cache things, it would cost too much and they couldn't make a living out of it.
To me, this shows that the actual service/content they're providing has relatively low value, and so they're "making" money not just on the content but also on the services side; eg, they're a cheaper sysadmin than an outsourced one. And they're also possibly ignoring risk; eg, they don't have the data durability that a cloud provider does, but it Probably Won't Matter (TM).
There's absolutely nothing wrong with this way of making money; the lower the margins, the more watching your costs is crucially important, and the difference between making a living and not even breaking even!
Possibly, it may also be that the cloud providers are offering things they don't need. Maybe that's uptime guarantees, potential scalability or integration with other services.
If you take SaaS, they are skewed towards buy, because their margin is ridiculously high. Better to hit the market now by using stable products than optimizing on spend.
The bigger you are and the more you can think about optimizing spend.
I think it is quite the opposite. Having worked in startups that were VC funded it seems they consider VC money free money and just spend a lot of it in infrastructure without the need to.
I know for a fact our bill was around 15-20k USD per month for running a webapp that could be ran in digital ocean 40 dollars/month.
For a lifestyle business without VC money to burn it makes all the difference.
Oh I've definitely seen that too. My example requires responsible (and smart) leadership. My thought is that optimizing costs engineering hours, which are much more expensive than paying for the service bills.
Took me 20 seconds to install twint, and start scraping.
Took me 20 minutes to install twitter-dump, and despite a successful twitter-dump auth, I end up with 'Request exception Forbidden {"errors":[{"code":200,"message":"Forbidden."}]}'.
Not going to spend time to fix that, I'll use the dirty solution that works.
it's a linux clone of autohotkey, meaning it lets you script your mouse/keyboard/windows using python. It can trigger the scripts using a keyboard shortcuts or by watching keywords in regular text. I use it to kill emai/phone/date quickly, or to automate combinations of actions in GUI that don't have macros.
youtube-dl
I travel a lot, with plenty of downtime. Downloading conferences from many video sites, or music, turns those otherwise wasted hours into learning experience, relaxation, etc.
dynalist
Favorite life organization app, that I use for shopping, restaurant idea, todo, etc. Basically half of my GTD is in there. It's much more productive than any system I tried before, and I tried a lot of them.
thunderbird
I have 20 email addresses, and this varies depending of my clients. Web base email are not up to the task, and I need offline search/archive capabilities. Thunderbird is the only mature cross platform app that does that correctly.
pulsesms
I have a rich social life, and this means organizing groups of people. Of course, they all have their different chat apps, social account, preferences. Some are using an old 3310. Some don't want to be on facebook, etc. SMS is the only things that works with everybody, but typing it on the phone is a pain. I have an android phone, so no imessage, but no google account, so no android message. Pulsms allows me to write message from my computer comfortably.
fdfind and ripgrep
I search stuff all the time, and since they are way faster type (because easier to remember), faster to execute, and have an output that is faster to read, cumulatively it saves a lot of time.
tilix
I don't use a tiling windows manager or tmux-like software, so I rely on tilix to provide a terminal a the press of a key, and to provide tabs and split screens.
black
Automatic formatting for python code. No parameters.
bitwarden
Or lastpass, or 1password. Any password manager really. But bitwarden is the latest I'm using. I'd also say "tetripin" for otp on the command line but it would not really make it up to 100 hours.
meld
It compares files or directory. It's not the best out there, but it works everywhere, so I don't have to wonder. I just install meld. I'd say reggexer for search and replace as well, but again, not saving 100 hours.
--
Of course I could say GNU/Linux, python, firefox and vscode, but it's a bit obvious. Probably the most productive softwares I use though.
Shouldn't the customer either be competent at configuring the system themselves or let somebody else do it (who will then ensure that the config is valid)?
Edit: I suppose you mean that the config format should be "user friendly". I guess it should, but I have personally had far fewer problems with YAML than with TOML.
We have schemas for some of our configs which is a level beyond linting. Trying to spread this more and more. Removes some classes of load errors with services.
Trying to get to almost jsonschema level without the complexity of specification and reuse with the actual code
JSON Spec for YAML files is neither ideal as there is no standard way to indicate, within the YAML file itself, which JSON schema to be read by parsers and editors to validate the document.
Sorry, but YAML is a disaster and YAML Lint and JSON Schema are weak attempts to improve it.
I'd be happy if YAML evolved to a true schema support, use of brackets or some other tip so white space wouldn't be meaningful, and silly things removed like three hundred ways to define Boolean values.
XML is way worse. An errant tab can totally screw over your config with no warnings. I've never needed a linter or had much trouble with JSON, explicit delimiters go a along way.
Its designed for shell usage, python, ruby and friends don't feel "native" in that manner and are simply akward for many cases by missing most improtant thing - pipeline. People use them because bash suck and because they want to be full stack.
Comparison with python actually helps to put Rust in a positive light. Compared to the Python 2/3 debacle, Rust managed to introduce a major new version with lots of new language features (edition) while making it: a) entirely opt-in, b) easy to update to with automated tooling, and c) compatible with previous versions.
Compare this to Python 3, which cannot load Python 2 libraries, cannot be converted automatically, and is now effectively required with the sunsetting of Python 2 in January of this year. Python has a lot of strengths, and I think 3 is way better than 2, but the transition was very painful.
Meanwhile, I have a crate I wrote a while back for 2015 nightly, and it took me less than an hour to get it up and running for 2018 stable. But I didn’t have to! Everyone using 2018 (nightly) could still use the crate even if I hadn’t converted it.
Small packages means more packages, and more packages compounds the dependency graph which:
- makes dependency resolution harder
- means more points of failure
- makes auditing difficult
- makes install time longer
- leads to harder maintenance and upgrade
This also causes heterogeneity in the mass of your dependencies:
- it splits the resources for documentation, testing, tutorial, etc
- it ensures very weak integration between various building blocks, forcing everyone to rebuild glue code again and again
- it makes discovering the proper solution to your problem harder as you must chose a combination of dependencies instead of one
- it makes contributing to the project harder, especially to junior profiles, and increases the price of on-boarding
- eventually, it leads to a culture that pushes the "libs versus frameworks" so far you never get a decent framework for anything. This is why there is no JS equivalent to RoR or Django.
There is, of course, a balance to reach. You don't want a lib that does everything.
Doesn't this happen because of package manager duplication? I think npm lets packages have their own copies of their dependencies. Since we have a lots of small, widely used packages, they get duplicated at numerous points in the dependency graph. The number of files and installation size explodes.
A big part is the development toolchain, which would be installed at a system level for most languages.
I started a vue project last night, npm install --production installs 4 packages. With dev dependencies, I get 2300 packages. Eslint, babel, webpack, etc bring in lots of luggage
BTW, I think 19000 is wrong, on a fresh node_modules I get:
$ npm install gatsby
...
+ [email protected]
added 1773 packages from 733 contributors
and audited 23706 packages in 52.317s
$ du -sh node_modules
245M node_modules
Not sure where the "audited" number comes from, but its not the number of install packages. I get 2737 directories containing a package.json, 1477 of which are uniq.