Live data from Hacker News

Thank you, GitHub

github.blog

441–450 of 460 posts

Re: Thank you, GitHub

#441
post #351

Earlier quoted context omitted.

I use Visual Studio to develop software ( C++ ) for Windows and Linux targets. I do not find it slow and rather than being "pain" it is actually way above other development IDEs in my opinion.

What's your cold boot time?

cold boot time is such a strange metric for an IDE. Do you spend your days closing and restarting yours ?

Hot reloading could be a better metric maybe ?

When I learnt to debug remote code from my Visual Studio, I was blown away. https://docs.microsoft.com/en-us/visualstudio/debugger/remot...

Re: Thank you, GitHub

#442
post #43

I'm kinda worried about GH now. I actually worked at MS over a decade ago. They had a pattern at the time which routinely drove their acquisitions into the ground. It went something like this: an acquisition happens, and in order for folks who matter to not jump ship immediately, the acquired company would be allowed to operate semi-autonomously for a while. A year, year and a half sharks from Microsoft proper would…

You forgot the part about "leveraging" Windows into places where the acquired company had previously determined it was wholly unsuitable. Gack, what a terrible company.

s/Windows/Azure/ and that's a bingo

Re: Thank you, GitHub

#443

Earlier quoted context omitted.

What's your cold boot time?

cold boot time is such a strange metric for an IDE. Do you spend your days closing and restarting yours ? Hot reloading could be a better metric maybe ? When I learnt to debug remote code from my Visual Studio, I was blown away. https://docs.microsoft.com/en-us/visualstudio/debugger/remot...

>"Hot reloading could be a better metric maybe"

I have it running for weeks sometimes. My development desktop has 128GB RAM so VS just stays there. I frankly do not care about hot/cold reload time of this IDE at all even though it is very fast in my case.

>"When I learnt to debug remote code from my Visual Studio, I was blown away."

You should try VS 2022 preview. All you need is SSH access on remote comp. You do not have to deploy anything to target. VS does everything it needs

Re: Thank you, GitHub

#444
post #406

Earlier quoted context omitted.

I don't see the reply I made here with that throwaway (shadowban?), so I'm doing it with my other one. > for HN to be a community, users need some identity for other users to relate to Apparently not! Using throwaways, people have upvoted me like crazy . Hundreds of points per month, for a person with no identity. If it kept going at the same pace, I would outrank some of the highest-point users within a year or two,…

You can't judge these things by upvotes alone. Indignation and flamebait routinely get upvoted, for example, and are obviously not what this site is for. The system is complex and upvotes are just one factor. https://hn.algolia.com/?dateRange=all&page=0&prefix=false&so... As for 'the community not disappearing' - this is a freerider argument. You're benefitting from the contributions of all the people who aren't beha…

So do you consider positive comments that get positive engagement to be a benefit to your community? If not, I get it, and your position is basically "I just don't like throwaways regardless of their contribution". But if that's not your position, you don't seem to have much of an argument yourself.

Also, there is no "freeriding" if the throwaways are actively producing positive content. You might as well call every single user a "freerider" - what are they contributing at all? Is your forum getting paid by someone based on an estimate of "real users" or something, and throwaways screw up your numbers? It really doesn't make sense.

The idea that a static username alone has an outsized positive effect on your community doesn't seem to be provable, in the face of accounts like mine. Maybe you're just making a general rule so you can eliminate the majority of accounts used for flaming or spam, I can't tell.

Re: Thank you, GitHub

#445
post #421

Earlier quoted context omitted.

> There is a good chunk of Iranian society that genuinely thinks their system is good, and it keeps the country somewhat stable in a region where such condition is not particularly common. That explains the massive exodus of talent, minds and people straight out of the country minutes after the revolution.

... which was 40 years ago. Quite a few people were born since then, and still live there. Obviously it's not a paradise, but it's not comparable with the likes of North Korea, and these days it's not that incredibly different from other supposedly-good countries in the region.

> Quite a few people were born since then, and still live there

And if you go to any western university campus, you'll meet many of them, born after the revolution, who worked hard to make it to the west and who are trying to sponsor their families to join them.

The opposite (westerners trying to do the same in Iran) is virtually unheard of.

Re: Thank you, GitHub

#446
post #400
post #365

Earlier quoted context omitted.

> That is a risk that is common to every single industry, and as such is a risk that is easily understood and quantifiable. Honestly: No If it would be "easily quantifiable", you would not see in 2021 still bank ATM running damn Windows XP or nuclear power plant under Win2000 with some old deprecated crap supervisor tools. It is a common drama with proprietary solutions, they are seducing to install and a nightmare t…

I don't understand. Is your claim that ATMs are running Windows XP because Microsoft did get buried under a pile of ash in the early '00s and released no further OS upgrades, and therefore it would have been better for the ATM manufacturer to use an open-source OS because they, unlike Windows, survived to 2021? Nobody in this thread is arguing that everything in the world is perfect. There are a lot of bad things in…

> The specific argument in this subthread is about whether it's okay to build your business on proprietary software or whether there's too much of a risk that the vendor will stop producing updates

It has everything to do with that and I think it's a way too narrow view.

In this case Microsoft indeed did not go bankrupt. They did however stopped to provide updates to solution "Windows XP", without giving an alternative compatible on the same legacy hardware (the old ATM hardware).

And that illustrates perfectly the problem with proprietary ecosystem. You do NOT need your provider to bankrupt to put yourself in shit, you just need him to have interests diverging of your interests.

Because at the end, he is the one controlling your software stack, not you.

Re: Thank you, GitHub

#447
post #365

Earlier quoted context omitted.

> That is a risk that is common to every single industry, and as such is a risk that is easily understood and quantifiable. Honestly: No If it would be "easily quantifiable", you would not see in 2021 still bank ATM running damn Windows XP or nuclear power plant under Win2000 with some old deprecated crap supervisor tools. It is a common drama with proprietary solutions, they are seducing to install and a nightmare t…

> If it would be "easily quantifiable", you would not see in 2021 still bank ATM running damn Windows XP or nuclear power plant under Win2000 with some old deprecated crap supervisor tools. > It is a common drama with proprietary solutions, they are seducing to install and a nightmare to maintain. The fact the software is "proprietary" or not is largely irrelevant to whether or not the systems-integrator who made tho…

> Had they chosen Linux then that ATM would still be sitting there with just-an-outdated version of some embedded Linux distro.

That's wrong, they would have been in a position to update / maintain themselves their own distro or dedicate that to a third party company that has the knowhow to do so. This for more than 20 years without problems. Because they would DO have the code for it if they want it.

With proprietary solutions in the embedded system world, this is impossible to do. If your providers refuses to support your OS anymore, you're fucked and that's it. And if he wants to increase the cost of your support maintenance program per 10x because it's legacy, you're fucked too, just in an other way.

> Linux because Linux does not have a stable applications ABI between major releases: the software would need to be recompiled.

I disagre and for two reasons:

- first, if it's your software stack recompiling should not be a problem

- second, it is not true. Kernel ABI is stable (mostly). And running statically compiled binary between major kernel releases never have been a problem.

> infrastructure operators are not going to be happy having to do patch-tuesday and recompiling their software on a regular basis for hardware they'd really prefer to leave alone and stable.

Do they ? Even on ATM, client software evolves and is updated. In their case, they just do it with the pain of a legacy system without being able to touch to the platform itself because they have no control on it.

Re: Thank you, GitHub

#448
post #365

Earlier quoted context omitted.

> That is a risk that is common to every single industry, and as such is a risk that is easily understood and quantifiable. Honestly: No If it would be "easily quantifiable", you would not see in 2021 still bank ATM running damn Windows XP or nuclear power plant under Win2000 with some old deprecated crap supervisor tools. It is a common drama with proprietary solutions, they are seducing to install and a nightmare t…

>If it would be "easily quantifiable", you would not see in 2021 still bank ATM running damn Windows XP or nuclear power plant under Win2000 with some old deprecated crap supervisor tools. Why would you not see that? The risk profile is well understood, and can be mitigated. Sandboxes, firewalls, app-containers, input sanitization, Virtual Machines, etc, etc, etc. I don't quite understand exactly what you're disagree…

> Why would you not see that? The risk profile is well understood, and can be mitigated.

So well understood that hacks on ATM happens every weeks :)

Re: Thank you, GitHub

#449
post #448

Earlier quoted context omitted.

>If it would be "easily quantifiable", you would not see in 2021 still bank ATM running damn Windows XP or nuclear power plant under Win2000 with some old deprecated crap supervisor tools. Why would you not see that? The risk profile is well understood, and can be mitigated. Sandboxes, firewalls, app-containers, input sanitization, Virtual Machines, etc, etc, etc. I don't quite understand exactly what you're disagree…

> Why would you not see that? The risk profile is well understood, and can be mitigated. So well understood that hacks on ATM happens every weeks :)

Which magical technology are you proposing that doesn't get hacked?

Re: Thank you, GitHub

#450
post #421

Earlier quoted context omitted.

... which was 40 years ago. Quite a few people were born since then, and still live there. Obviously it's not a paradise, but it's not comparable with the likes of North Korea, and these days it's not that incredibly different from other supposedly-good countries in the region.

> Quite a few people were born since then, and still live there And if you go to any western university campus, you'll meet many of them, born after the revolution, who worked hard to make it to the west and who are trying to sponsor their families to join them. The opposite (westerners trying to do the same in Iran) is virtually unheard of.

And? Nobody said the Iranian system is some model of virtue, just that it isn't so incredibly bad that the alternative of "start a bloody civil war and ruin the whole country for decades" (the Libyan experience) can realistically be considered attractive by most of the population.
Post reply on HN