20×10%
lars.ingebrigtsen.no
lars.ingebrigtsen.no
It worked miracles, with minor-but-irritating bugs getting solved much faster, and with features for niche groups getting implemented as opposed to laying in wait for a bigger project it would thematically fit in.
Some devs even went out of their way to spend those two weeks on a single, irritating, deeply-rooted bug that nobody in their right mind would even want to fix.
I worked at a place once where my favorite time was at the end of the year; most people were off on vacation but they needed a skeleton crew in case of issues. This was when we did tons of small bugfixes, improvements and refactorings, and honestly that's the best part of the job IMO. Screw building features and adding customer value, just let me do janitorial jobs :D
I personally like it because the issues are more diverse and I get to pick. For example, my last task was something a colleague complained about in a reporting tool that was also bothering me and I also got to learn something new
"The British government, concerned about the number of venomous cobras in Delhi, offered a bounty for every dead cobra. Initially, this was a successful strategy; large numbers of snakes were killed for the reward. Eventually, however, enterprising people began to breed cobras for the income. When the government became aware of this, the reward program was scrapped. When cobra breeders set their now-worthless snakes free, the wild cobra population further increased."
:/
Sometimes, we would “invent” something novel and truly impressive that would open doors to future features that were previously impossible.
It's amazing what we live with in tech debt and what a clean environment would enable.
https://lars.ingebrigtsen.no/category/emacs/
A banking CTO who contributes a lot in emacs.
I really like the image editing he did. Thank you for posting this. Made my day.
1. A suit-wearing person that's so far removed from technology he's just a glorified manager hunt-and-pecking in Outlook all day.
2. A suit-wearing person with a permanent PuTTY window connected to the ageing AS-400 system still running in the basement.
It automatically ensues positive image and accelerates advancement of humanity in science and tech, especially for programs that are core to everyday life of developers, like editors.
Someone tag Mr Musk.
You can see this with Microsoft. Most people have no idea that "Microsoft Loves Open Source" is a thing. A few people seem to think Microsoft deserve the benefit of the doubt, some view it from a purely pragmatic view, and some will never forget "embrace, extend, extinguish."
The practical benefits might end up worthwhile for them though.
Of course it's not a binary thing for most people of flipping from "MS bad!" to "MS good!", some already liked MS and like them even more, some still hate them, still say "why should I trust them given their history / given they're not 100% lovely even now", but still surely a bit less hate than if they were still acting as they did 20-30 years ago.
I've no idea if my gut feeling is more or less right than yours, Id imagine companies as big as MS do actually do research to see how things like this affect public perception (not just for end users/businesses but also for tech workers), but I'm not aware of any research being made public on the PR benefits (or lack thereof) from contributing to open source stuff.
They owe it to the open source community; they built trillion-dollar companies on top of open source.
There are incentives to open source platforms so that they can build applications on top, support projects so that they can steer them etc. but they don't owe anything to the original developers.
From that perspective, taking software that has been expressly allowed (in black and white) to be used with more or less no restrictions and without any need to give back is perfectly fine (and in some sense, even moral) as far the corporation and the code by which it functions is concerned. That's how I see it.
If the open source movement is interested in being sustainable etc., the licenses should bake in some kind of clause that incentivises the companies to pay back either monetarily or with effort. Of course, that would hurt their adoption so they choose not to but if they do that, they can't really complain when companies just take their work and use it many times without even an attribution.
Happy Emacs user here and excited/grateful to see how well the ecosystem is currently doing.
Emacs bugs I've reported can vary from "I'd like this behaviour" to "something ain't right here" to "docs are borked on <subject>". Emacs is so stable there's not many crashing bugs to report.
Emacs devs are great btw, tolerant of occasional n00bishness and very responsive.
If you can repeat a crash, please do report it.
If you allow networking, you can do emails like gnus.
If you allow pictures and HTML parsing, you can do a web browser like eww.
I guess you don't have to add too much to get a new domain.
The beauty of emacs is how easy it is to modify it. Lisp is the easiest syntax to learn, emacs hides nothing from the user, and the user can override or add whatever they wish. It really is a proper example of free and open software. To add to this, it's all very well documented, and everything you need to develop (for) emacs is in emacs itself.
- image cropping in an image viewer is useful if you'd like to quickly crop screenshots before posting,
- you can already view images in emacs.
So the irksome bloat is likely already there, and stems from emacs not only being a text editor, but an operating system onto itself.
While it is true that dedicated applications are usually more capable and convenient for specialised tasks, having tools integrated together like in Emacs also has its strengths (e.g. it can allow for heavy scripting of a workflow).
https://github.com/alexmurray/emacs-snap
I am using it as a daily driver for months already without issues so far.
Download from https://github.com/kiennq/emacs-build/releases
Unzip into a folder of your liking, C:\Users\<username>\AppData\Local\Emacs would be a sensible start
I much prefer the full chart. Of course one could say that they dont see the details in the full chart, but it is not the situation here.
Also good work.
I hope somebody checked the bugociraptor fences.