526 karma · joined September 30, 2014
I'm afraid this could result in even less support from the governments and/or less effort to reduce emissions and other climate-changing actions. Which could be disastrous at the end of the ~ 40 years...
Also, seems like a translation string is missing for vim (displayed as "tools.vim" in Other Tools > Text Editors)
[0]: https://haxe.org/
Like you are used to do it in something like 25 minutes with a car, even though there could be near-instant methods of travel available (it's science fiction but still to the point: when you don't have (or don't have any more, for some time) a better alternative, you can overlook many inconveniences).
Is there some data on the actual scale of individual vs corporate pollution / climate-changing faults? Hard to measure, I guess.
On a more serious note:
1. have one less kid.
I really don't like how this one is worded, I always read it as "get rid of one of your kids". Though, except going from 1 to 0, it's not that bad. I definitely wanted more than one, but I can settle with the one I have.
2. go carless
You get used to it. I even lived in small cities (~30k inhabitants) and while it's harder when your city isn't supporting a carless lifestyle (never lived in any that does that, sadly), it's definitely doable.
3. don't travel
Maybe a bit extreme to give it up entirely. But you can still travel less, do it with more eco-friendly travel options (carpooling, etc.) or go to destinations which do not require planes. I guess it depends on where you live, but in Europe there's definitely lots of wonderful places I can go to with a low carbon impact.
But I still am responsible for a lot more carbon emission than I should. I'm taking it slow (changing food habits, etc.) but there's still domains in which I am really bad (using too much tech, ordering things online..).
> We continue to monitor restores which are taking longer than anticipated. We estimate they will be caught up in an hour and a half.
> At 10:52 pm Sunday UTC, multiple services on GitHub.com were affected by a network partition and subsequent database failure resulting in inconsistent information being presented on our website. Out of an abundance of caution we have taken steps to ensure the integrity of your data, including pausing webhook events and other internal processing systems.
> We are aware of how important our services are to your development workflows and are actively working to establish an estimated timeframe for full recovery. We will share this information with you as soon as it is available. During this time, information displayed on GitHub.com is likely to appear out of date; however no data was lost. Once service is fully restored, everything should appear as expected. Further, this incident only impacted website metadata stored in our MySQL databases, such as issues and pull requests. Git repository data remains unaffected and has been available throughout the incident.
> We will continue to provide updates and an estimated time to resolution via our status page.
As for this:
> Who will be woken up at night when there's an outage?
Unless they are working with teams around the world, does it matter if their server is down the whole night, as long as they can get it back up first thing in the morning?
*: Well, sort of.. there are bits scattered everywhere, I had to dig into email archives to find some specifications.
This is totally personal and subjective, but I'd say that a website is defined by its content, while a web application is defined by its interaction with the user. That is, a website can plausibly consist of a static content repository that's dealt out to all visitors, while a web application depends on interaction and requires programmatic user input and data processing.
For example, a news site would be a "website", but a spreadsheet or a collaborative calendar would be web "applications". The news site shows essentially the same information to all visitors, while the calendar processes individual data.
Practically, most websites with quickly changing content will also rely on a sophisticated programmatic (and/or database) backend, but at least in principle they're only defined by their output. The web application on the other hand is essentially a program that runs remotely, and it depends fundamentally on a processing and a data storage backend.
I see React as a tool for building web applications, not websites. Using it for something like hacker news is not needed nor worth it, except for learning purposes or for the sake of using your favorite tech (which has its pros and cons).
Edit: I use React a lot, and really like it. It's just not the perfect tool for everything, and by no means a necessary one (at least when you don't have much complexity); even if it is a good one in many cases.
In the case of HN, seeing the current js [1] I find it pretty obvious that no "big tool" like React is necessary. It doesn't mean using React for a HN clone is a bad thing, one just don't have to.
[1]: https://news.ycombinator.com/item?id=17915560&goto=news
I planned on using both at first when I started migrating to graphql, but quickly saw that indeed redux was becoming redundant when we use apollo. Especially since they added local state management [1].
[1]: https://www.apollographql.com/docs/react/essentials/local-st...
Looked promising, though.
It's just nitpicking; with the example it's pretty clear that it's the icon font that is bugging you.
Overall it's a great improvement. I just hope this improvement doesn't come with regressions (more [e-]smokers, especially in public areas and maybe in newer generations) precisely because it is so great an improvement.
> However, Public Health England advises they are much less harmful than smoking and people should not hesitate to use them as an aid to giving up cigarettes.
-
What annoys me, though, is that while cigarettes are banned on most public places here (in France), people tend to use e-cigarette anywhere from work (open space) to transports, restaurants, bars, etc.
If they can't stop smoking, it seems to be better for them to be "vaping", but they should stop forcing us to endure their chemicals (although I'm not sure if this can be toxic for people around - but that's more or less the point too: we don't really know what it does to our body, so it shouldn't be allowed everywhere).
We've already fought cigarettes (well, I'm an ex smoker so I shouldn't really say "we" here), we shouldn't have to start over again for another form of smoking.
But any action I want to be made on the repository, I do it myself.
I have some exceptions though, like if I want to revert the hunk I have the cursor on it's nice to be able to revert (or even stage, but I still use `git add --patch` for that) it with one shortcut.
Seemed easy at first (got the first 5 right), but I guess that was mostly luck because I got a lot of the next ones wrong.
Edit: being from France, pokemon here have different names, making the english names less recognizable (I never played the games anyway so that doesn't change much for me)
Edit: * Well no, "simplicity" does not exactly mean what I first thought it did. I guess I mostly traded ease of configuration / usage. Openbox and i3 are more difficult to approach but they don't lack on simplicity at all.
To see such poor UX on the website of someone developing an OS is a red flag for me.
The haxe->js community is growing these past years, but I still think Haxe isn't getting the love it deserves (compared to TypeScript, Flow typing for react, etc.)