Hacker Newsnew | past | comments | ask | show | jobs | submit | nguoi's commentslogin

>So far China doesn't look very interested in climate change either

I disagree with this, I think it's easy to paint China as the villain across a cultural, lingual divide in an attempt to make the case that one's own obligations to reduce emissions don't matter. China has a carbon market now and produces more nuclear power than any other country. Climate change is a very real problem for a country with an encroaching desert.


Unfortunately, I do need to go to work if I'm interested in continuing to live.


Walk/drive/train/bus are options too.


2hrs/Illegal for medical reasons/doesn't exist/doesn't exist


I think you should have indicated that you weren't certain in the original accusation.


I'm not sure if you caught the above comment but I can be certain that professonal services staff (HR, admin etc) who's accounts have been used by Scihub definitely did not give their credentials voluntarily. They have zero interest in Scihub or access to material.


Some of the same websites also break middle click functionality. Sometimes, if you fail to load the next 'page', you can't have another go at loading it unless you refresh and scroll down n 'pages' again.

Facebook has the most Fun with tabs: you go to the new tab and wait for it to load everything. And then it loads everything again in a slightly different overlay! You have to open it in a new tab, of course, or the video you're trying to watch will vibrate around your screen from comment sections growing above it, and pop out into a different view.


Players didn't have to aim up to shoot something above them


I used to be weekend staff at a clothing store that changed layouts every week. Every weekend, I'd have to relearn where everything was.


Inline was added in C99, which MSVC still doesn't support entirely. If this has to be taken into account when you choose what standard to use for your codebase, that's a quarter of a century trickle down for features to reach the consumer.

I hope I get to use C2x* before I retire.

*postmodern C?


The Microsoft C compiler actually has pretty good C99 support since VS2015 (e.g. inline is definitely supported).

AFAIK the only non-supported C99 features in the C compiler are VLAs (optional since C11 anyway), and type-generic macros (those would be good to have though).

Of course it would be nice if Microsoft gave the C compiler a bit more love, especially since it's much less work keeping a C compiler uptodate than a C++ compiler, but at least we got "most of C99".


The quarter of a century thing does not apply to "inline".

Although inline was added in C99, it was already an extremely widely supported extension in mainstream compilers, even since the C89 days, when we just called it "ANSI C".

MSVC has supported inline for a long time, long before it started supporting other C99 features.


That doesn't matter if features you're able to used are gated on the standard you use. If the standard you choose is based on what your target platforms 'support': no inline for you.


It seems weird to decide that you won't use features because they are in a public standard that your target platform doesn't support, even though your target platform fully supports those features themselves.

I could understand the concern if it was about portability to other target platforms, or keeping the option of doing so. But in that case, the public standard your current target supports is irrelevant.


It happens. Imagine you decide on the MS-compatible bits C99, then the team naturally picks up new people and loses the ones who made the decision. Eventually, people will know the standard is C99 from the build system but not the reason behind the decision.

So they add a feature not supported by MSVC and don't learn that it doesn't work until someone else tries to build on Windows.

If you choose to use features based on whether they work or not, you don't need to choose a standard at all. But that loses you all of the guarantees a standard provides.


Fundamentally, I think you are correct, however my English-second-language friends/colleagues tend to write better English when it's in a structured fashion - like a commit message or in documentation - than they do colloquially. That is how they learned it, after all, while native speakers learn it from osmosis. It's rare to see the ESL speakers use the wrong there/their/they're like native speakers do.


I suspect 'The Hague' from the byline is not in a country with a murder rate double that of the Netherlands.


I thought Linux didn't provide a stable ABI and tells developers to upstream instead? Is this the same topic?


The article is about OS ABI for applications (which Linux has), not internal OS ABI for drivers (which Linux hasn't).


Linux doesn't have it, but Linux Trebelized has it.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: