2,203 karma · joined September 28, 2017
> The free software movement gave me an operating system and critical applications so I can do my work without big company garbage interfering.
[...]
> Because this is onerous software developers who seriously wish for success and profit minimize exposure to copylefted source code.
I couldn't say them without feeling I'm internally adopting a double moral standard in order to justify my goals.
If your application is a client-side GUI you may not want to restart it on reconfiguration. This applies to other things as well: think about having to restart your reverse proxy/load balancer each time you add a new route, or rebooting your OS each time you reconfigure a systemd unit, or reinitializing your embedded HW because something changes. The possible incarnations of SW are very much varied, and not everything can be solved in the same way.
- clear error messages (with the actual data that caused it, minus privacy-sensitive information) - possibility of reloading configuration without having to restart the whole application (configure-once-at-construction-time is not enough; not every application is a web application with a php-like lifecycle)
- atomic check pointing and restoring of long running operations, without leaving a trail of partially truncatd temporary files
- security: you do not know how to write secure software until someone hacks your software in an unexpected way. This includes knowing how actual infrastructure configuration affects the running software (symlinks, permissions, capabilities)
- performance: unless "scale" a software means blindly increasing the number of replicas, there are so many architectural lessons to be learned studying flame graphs of actually running software that it is hard to imagine to acquire those expertise without making your hands dirty. At that point, it is even possible that your software works so well it no longer needs so much hardware
I've ben using Meld daily for more than 10 years now. I am not so sure it can be defined "performant". Maybe your box is really powerful, but on small and mid-sized systems its performance is more on the clunky side.
I remember its performance worsened when it migrated to GTK3. It has stayed semi-slow for me since then.
How badly Mozilla messed up with Firefox on Android is worth another topic, however.
[0] https://addons.mozilla.org/it/android/addon/video-background...
If you are comparing electric capacitances of electric circuits vs the thermal capacitance of a macroscopic object, 1 Hz might be a high enough frequency for doing pwm.
But it is true that, for the mindset of the general public (or younger developers), it might well be nonexistent.
It is a shame, since life with mercurial is still so easier.
You can also have a look at "generator expressions", which are the lazy counterpart to a list comprehension (hint: use " ()" instead of "[]").
I'd rather work on better mentoring the single members.
This is if you do not care writing any logic. If you do, there are other possibilities, for example using a queue and a a dedicated thread for handling database access, but I personally do not think there are many advantages to this more complicated approach.
Have you considered stored compressed blobs in a sqlite file? Works fine for me, you can do indexed searches on your "stored" data, and can extract single pages if you want.
> sudo curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/in... | /bin/bash
piping the output of a curl command to sh without first checking the sha256 of the file you just got?
In a similar situation I would not be comfortable without at least getting a specific version of the tool I'm downloading and then hardcoding an hash of its content I computed after manually downloading and inspecting its content.
An old Ars Technica article comparing the two protocols (much has changed since then): https://arstechnica.com/information-technology/2010/10/ars-e...
Keyword removal totally dumbed down my browsing experience on mobile. I fear the moment the same will happen on the Desktop version.
Not every occasional contributor will become a project member, so it makes no sense to impose too much burden on him. Maybe he only wants an interesting feature added.
Some of them will eventually become interested in becoming regular contributors, and that is even better, but every one should be left freedom of choice.
In my experience as Etherpad maintainer (1.6.5 through 1.8.4) this approach worked very well. For example https://github.com/ether/etherpad-lite/issues/3540 (and the related PR https://github.com/ether/etherpad-lite/pull/3559) where deep changes that went very smooth, not only code wise, but above all wrt the relation with the contributor, who was smart and collaborative.
No need to sign in to YT.
https://upload.wikimedia.org/wikipedia/commons/d/d7/Experime...
What are the curly braces around the URL in <a>'s href attribute? Is there a spec for it?