We had a very nice experience (keeping the video stream at minimum), and friends abroad were able to join us!
I only missed the pizza together 😄
like this
They simply declared what they wanted to happen, entering into a negotiation with the borrow checker, and then revised their design until both parties were left satisfied.
It's #InCoWriMo!
First letter delivered, and I may have changed my avatar a bit for the season :)
(and doing this feels wrong, as if I was sharing publicly a symmetric encryption key…)
Benno Ricesystemd is, to put it mildly, controversial. As a FreeBSD developer I decided I wanted to know why.
I delved into the history of bootstrap systems, and even the history of UNIX and other contemporary operating systems, to try and work out why something like systemd was seem as necessary, if not desirable. I also tried to work out why so many people found it so upsetting, annoying, or otherwise rage-inducing.
Join me on a journey through the bootstrap process, the history of init, the reasons why change can be scary, and the discovery of a part of your OS you may not even know existed.
like this
scene: inside valhalla's brain.
home economy manager> I know that #InCoWriMo is near, but you can't buy new stationery until you've used up the one you have. Not even if it's cheap, you no longer have space to keep it
some other less wholesome part of me> making doesn't count as buying, right?
home economy manager> well, since you're using things you already had in the stationery bag…
(I had a 2015 sponsored calendar together with stationery and other paper “in case I ever decide to do something with it”)
Thunderbird calendar addon Year View is now in "(very) low maintenance mode".
It will not be updated to support TB68 or TB70.
As the readme says, I don't have time, resources and motivation to keep work on this.
I'm not really using this plugin anymore from a while now.
I'm using TB only on my office Mac, where I'm still on TB60 because 90% of the addons I need still doesn't work in a way or another on TB68.
Writing "Year View" was a quite painful experience: overall documentation was too old ad outdated or non existent. And that's only on Thunderbird/XUL side: I had to read and understand Lightning code because I couldn't find any other docs. Most of the code in "Year View" is an edited copy of Lightning code. There are also a number of ugly hacks.
From what I read in Thunderbird docs, if I manage to make this thing run on TB68 I will need to rewrite it anyway to make it run on TB70 (where my needed addons will not run anyway). I'm very sorry, but It's not worth the pain.
If you want a proper year view in calendar in the future, please bugs Lightning devs.
finishes writing a letter.
looks at the calendar.
I guess it's time to start to work on the list of people I want to write to for #InCoWriMo (and to see if I have enough stationery, but I probably do :D )
About one year ago, my father gave me and @Diego Roversi a cheap laptop he had bought at a supermarket and found out it wasn't suited to his needs (plus it didn't have enough disk space to install the latest windows upgrades, or something like that, I don't remember the exact details).
We didn't really have a need for it, the only part that was potentially interesting (touchscreen and tablet mode) didn't work with linux, nor did the sound card, and overall the process to install linux on it made us discover how low quality the thing was, but we ended up using it to watch movies with an usb sound card.
Then the last time we tried to turn it on (to show a countdown for the new year) it didn't. Opening it revealed a dead battery. Glued down to everything else. And it didn't start without a battery connected. And when trying to unglue the battery it started to break, so my SO stopped before burning down the house.
At this step, #repair mode ended and scavenging for parts started, but most components were covered by the glued-down battery, trying to dismantle the screen resulted in cracked glass and the only thing we could save are two magnets and a handful of screws.
We didn't buy the thing. We didn't need the thing. We knew it was bad, but still this is irritating. Extremely irritating.
it did.
except for the fact that we aren't going to buy a new one to replace it (but I suspect my father did).
OTOH, reading point 3 of the proposed solutions and comparing it with the place I'm getting my dependencies from (distributions):
For example, package discovery sites might work to find more ways to allow developers to share their findings.
check, there is room for improvement, but the principle is there and is being used
Build tools should, at the least, make it easy to run a package’s own tests.
check
More aggressively, build tools and package management systems could also work together to allow package authors to test new changes against all public clients of their APIs.
check, as long as those clients are also available from the same source
Languages should also provide easy ways to isolate a suspect package.
this one isn't done, but the idea is that suspect packages don't get there in the first place. YMMV on what counts as suspect, however.
Elena ``of Valhalla''
in reply to Fabio • •next time we can coordinate and order pizza from a local delivery place.
Except for the person abroad, for whom delivery pizza is an expensive treat, unless they learn how to bake it themselves (the source code for my pizza is available) :D
ictus
in reply to Fabio • •Fabio
in reply to Fabio • •yes. also for me.
Never heard of.
Anyway, Jitsi Meet it's fully opensource and self-hostable. Don't see any problem..
Fabio
in reply to Fabio • •Found:
jitsi.org/news/we-have-a-new-h…
"from Atlassian" looks like an improvement, to me.
Again, all the source code is available :)
ictus
in reply to Fabio • •