For my VPS, I have a Notion page where each project (name, url, mapped ports) is a row in a table. Then the project page contains a copy of my docker config and various informations I might need for maintenance/reinstallation.
596 karma · joined March 11, 2015
For my VPS, I have a Notion page where each project (name, url, mapped ports) is a row in a table. Then the project page contains a copy of my docker config and various informations I might need for maintenance/reinstallation.
The comment I was replying to was saying:
> there is so much js tooling and documentation and of such wide variety that a year or two would not be enough for even a light review
There's no need to learn the entire ever-evolving JS ecosystem. You pick a sane starting point (a framework tutorial) to get you up and running in a few days, and from there you learn what you _need_.
Of course if you've never written a line of code in your life, or if you're angry at the thought of using a dependency manager, you're going to have a hard time. And not only with the web stack.
I didn't know that mercurial had a web interface, I'll certainly take a look this week.
- "relatively new project" > code is fresh and certainly well-organized / maybe lacks stability
- "all by one person" > a single vision is a good thing / if that person gives up the project, it's dead
- "no other project mentions it" > [no good aspect in that] / no real-world usage
If you have any experience in the frontend field, those points are more often bad than good. You don't want to invest time and/or money in that kind of project that has a high chance of being dead within a year.
Now, that does not mean that it's a bad project (it looks pretty good actually), but it's just very young.
Edit: actually I like this framework very much (but I have a thing for underdogs). It might be ideal to quickly throw POCs or toy projects
I could see this as a useful feature when you need to chat with contributors once in a while in a less-formal way than issue comments.
They absolutely don't. There's no art collectors or amateurs in this game, only speculators.
> He should have counted 0, 1, 2, 3
Is that how _you_ count? You imagine some pointer going _between_ items, start at zero, and stop once you have nothing at the right of your pointer?
Or, little Timmy could also skip the "zero" part (because you know, he's not dumb nor blind, and sees that he has several pens on his desk), start at 1 while pointing _at_ the first pen, and count up to 3.
Seriously?
- "Hey Timmy, how many pens do you have on your desk?"
- "Let's count them! Zero, One, Two."
- "So how many is that?"
- "Well since I ended my counting sequence with 'two', it totally makes sense to announce that I have three pens."
You can be registered on different instances, but they're all different accounts. The Fediverse "only" allows instances to share content with each other.
> This part confused me a bit. Can anyone ELI5?
If Mastodon instances A and B are connected through the Fediverse, you can _read_ content posted on B if you're registered on A.
The best analogy I've seen is to consider Fediverse servers like e-mail servers. You can post an e-mail from a server only if you have an account on it, but you can receive e-mails from any server.
And if the OS decides to kill your app's process, your polling dies with it and you don't get notifications.
I switched from Notion to my own electron-based markdown editor just for the peace of mind of not having my notes stored in clear on someone else's server.
The cookie banner that you have to refuse/accept only concerns cookies that are not necessary for the proper functioning of the site. So login cookies or shopping cart are unaffected by the consent, and if your site has nothing else than this, it does not need to ask for consent.
If you call a Mac a PC, you'll only confuse your interlocutor. No-one ever refers to Macs as "PC", except to point out that "Macs are 'Personal Computers'".
TIC-80 is less restricting: more languages (Lua, MoonScript, JavaScript, Fennel, Wren), custom color palette, higher res, and widescreen. The main advantage of PICO-8 is its community, which is the biggest of all "fantasy consoles", which means more help, more examples, and more released games.
I'd personally go with PICO-8, because it's more restricting, and thus allows for a better focus (IMO).
And since JavaScript implies TypeScript, I once wrote a small tool to automatically build games from .ts files, with functions declarations for the whole API: https://github.com/scambier/tic80-typescript
I don't use it anymore, but try to keep the declarations up-to-date :)
So yeah, decimals are so used that you don't even need to tell the unit, it's implicit. I once had an american argue with me about Fahrenheit vs Celsius, because "Fahrenheit is more precise". I guess he was either a superhuman who can feel the difference between 20°C and 21°C, or someone who never heard about decimals.
And more importantly, even if the risk of death is low for me, I can still transmit it to high risk people.
The article I linked is literally titled "Why Belgium's death rate is so high", you didn't even took the time to just click on it before replying to me.
Here's another, more recent article, in case you'd want to know more, and how our "over" counting effectively hurts our international image: https://www.dw.com/en/belgiums-coronavirus-overcounting-cont...
I'm just tired with people taking Belgium as a "worse situation" example, while our lockdown had been quite successful in flattening the curve. A counterpoint though, we really badly handled the nursing homes, and most of our deaths come from there.
You cannot compare two countries without taking more things than two numbers into account.
Relevant excerpts:
> The term employs traditional light-versus-darkness imagery to contrast the era's "darkness" (lack of records) with earlier and later periods of "light" (abundance of records)
> As the accomplishments of the era came to be better understood in the 19th and 20th centuries, scholars began restricting the "Dark Ages" appellation to the Early Middle Ages (c. 5th–10th century),[6][7][8] and now scholars also reject its usage in this period.[9] The majority of modern scholars avoid the term altogether due to its negative connotations, finding it misleading and inaccurate.
Wow. I have a hard time imagining being an interviewer and literally laughing at the face of a candidate before he even said anything. Unless he's dressed as a clown or something...