Not sure why you would ever need to think (let alone curse about) what the separator is for a particular OS when you can call path.join or path.split and let it be someone else's problem.
Because I work on code that is built for a half-dozen different operating systems and platforms, and that code has to do a lot more with paths than joining or splitting them. There are appropriate library functions available on all the platforms. Yes, there should be, and developing a common library is on our to-do list, but that's a fairly major task all by itself.
Think about it. Why is this linky linky thing stupid? Put another way: What would have been better?
What would have been better is to follow standard practice with important domain names: you register the name you want as well as all of the variations/typos that might be easily confused with it.
It's called a NMI, or non-maskable interrupt... except... it actually isn't one of those, at least not at the hardware level.
Well, at the CPU level, it really is a non-maskable interrupt. The CPU interrupt mask can't mask it. But the usual IBM-style architecture runs the interrupt line through an external interrupt controller before it goes to the CPU, and it can be masked by that.
Consider: what's the big O efficiency of a particular algorithm?
When I do interviews, I have a couple of "sanity check" problems that I use to try to weed out the candidates who may be great at crafting code, but not great at designing software. A big-O problem is one of these.
Pretty much. What an employer wants to know is if you are skilled enough for the position. A degree provides assurance of at least a minimum level of skill, but demonstrating the required skill through through experience is just as good (or better, if the candidate is a recent grad. They always need additional training.) That's why most jobs ask for a minimum degree "or equivalent experience".
Generally speaking, if you have serious experience then a degree is of minimal or no value. If you have a medium level of experience, then a degree is helpful but optional (skill-specific certifications can be of more value in this case). If you have little or no experience, then a degree is essential.
Whichever way you go, though, there are no guarantees. There are a million reasons why you might not get the job that are unrelated to your experience or education.
I may be misremembering -- it was a long time ago -- but I think that the original IBM BIOS implemented the handling of Control-Alt-Delete, so it was effectively baked in. The OS could (and did) hook it, but if the OS did nothing, Control-Alt-Delete still worked.
I believe this remains true to this day, which is why the key combo works even before the operating system boots.
Yes, I agree that Control-Alt-Delete is an entirely reasonable design, and I'm not sure why Gates is apologizing for it -- particularly when there are a number of other things that I think most people would agree he should apologize for.
For instance -- using the backslash for directory paths when every other OS used normal slashes. As a developer, I think I curse that about once per week.
I thought the point of Ctrl-Alt-Del was that it generated a system-level interrupt that no other program would be allowed to supercede
It generates a non-maskable interrupt. However, under the IBM architecture, it has always been possible to install your own handler for that interrupt (and it's always been possible to mask it).
With the uniform, badge, hardhat and clipboard, he could walk into any boarding to look at electrical closets and no one would question him.
I can do you better than that. In a prior lifetime, I was a janitor. I learned that if you look dirty, harried, purposeful, and carry a mop and a big ring of keys on your hip (that part may have changed since then), you become entirely invisible and can wander anywhere without being challenged.
And here I thought that everyone went through the Settings app to begin with. I always have.
People tend to think that the way they do things is pretty much the same as the way most other people do things. This assumption is seductive, but often very incorrect.
"There are appropriate library functions" should be "There aren't appropriate library functions"
Not sure why you would ever need to think (let alone curse about) what the separator is for a particular OS when you can call path.join or path.split and let it be someone else's problem.
Because I work on code that is built for a half-dozen different operating systems and platforms, and that code has to do a lot more with paths than joining or splitting them. There are appropriate library functions available on all the platforms. Yes, there should be, and developing a common library is on our to-do list, but that's a fairly major task all by itself.
Think about it. Why is this linky linky thing stupid? Put another way: What would have been better?
What would have been better is to follow standard practice with important domain names: you register the name you want as well as all of the variations/typos that might be easily confused with it.
Typosquatting isn't anything like a new thing.
Yes, I shouldn't have said "all other OSes". I really meant the OSes that DOS was based on: Unix and CP/M.
It's called a NMI, or non-maskable interrupt... except... it actually isn't one of those, at least not at the hardware level.
Well, at the CPU level, it really is a non-maskable interrupt. The CPU interrupt mask can't mask it. But the usual IBM-style architecture runs the interrupt line through an external interrupt controller before it goes to the CPU, and it can be masked by that.
Back in the late '60s (Minsky's "first period") a 4-year CS degree actually HURT employability.
This was true all the way through the '80s.
Consider: what's the big O efficiency of a particular algorithm?
When I do interviews, I have a couple of "sanity check" problems that I use to try to weed out the candidates who may be great at crafting code, but not great at designing software. A big-O problem is one of these.
Pretty much. What an employer wants to know is if you are skilled enough for the position. A degree provides assurance of at least a minimum level of skill, but demonstrating the required skill through through experience is just as good (or better, if the candidate is a recent grad. They always need additional training.) That's why most jobs ask for a minimum degree "or equivalent experience".
Generally speaking, if you have serious experience then a degree is of minimal or no value. If you have a medium level of experience, then a degree is helpful but optional (skill-specific certifications can be of more value in this case). If you have little or no experience, then a degree is essential.
Whichever way you go, though, there are no guarantees. There are a million reasons why you might not get the job that are unrelated to your experience or education.
I may be misremembering -- it was a long time ago -- but I think that the original IBM BIOS implemented the handling of Control-Alt-Delete, so it was effectively baked in. The OS could (and did) hook it, but if the OS did nothing, Control-Alt-Delete still worked.
I believe this remains true to this day, which is why the key combo works even before the operating system boots.
Yes, I agree that Control-Alt-Delete is an entirely reasonable design, and I'm not sure why Gates is apologizing for it -- particularly when there are a number of other things that I think most people would agree he should apologize for.
For instance -- using the backslash for directory paths when every other OS used normal slashes. As a developer, I think I curse that about once per week.
Or, maybe more controversially, the registry.
I thought the point of Ctrl-Alt-Del was that it generated a system-level interrupt that no other program would be allowed to supercede
It generates a non-maskable interrupt. However, under the IBM architecture, it has always been possible to install your own handler for that interrupt (and it's always been possible to mask it).
What's wrong with Alt-F4? I use it all the time.
This was my reaction exactly.
press the close door button. Door will close predictably sooner (time it if you like).
In some elevators, yes. In others, no.
For the data
There was a lot useful in Google Glass, mostly around AR. The reason it failed wasn't a lack of usefulness.
Take Google Glass and literally remove everything that made it useful. Sounds like a win!
With the uniform, badge, hardhat and clipboard, he could walk into any boarding to look at electrical closets and no one would question him.
I can do you better than that. In a prior lifetime, I was a janitor. I learned that if you look dirty, harried, purposeful, and carry a mop and a big ring of keys on your hip (that part may have changed since then), you become entirely invisible and can wander anywhere without being challenged.
And here I thought that everyone went through the Settings app to begin with. I always have.
People tend to think that the way they do things is pretty much the same as the way most other people do things. This assumption is seductive, but often very incorrect.
I have great difficulty believing that, considering that there has been virtually zero innovation since Jobs died.
I don't see how that relates to the issue of whether or not Jobs was an engineer.
Sounds like a bug in either your device or LineageOS. You might want to submit a bug report about that.
I know that on my android phone, turning off the radios actually turns off the radios.
Having those qualities does not make you an engineer.
You put your finger on what Jobs really was: an industrial designer. Even he would never have claimed to be an engineer.
Are you saying that you think this is the result of malice?
Indeed, I wasn't claiming that they didn't exist. Those are the corners of the internet that are the most useful to me.
Looks like you don't belong to any nation that has an army.
You've moved the goalposts here. He said he didn't "support any person or group that uses violence...".
Belonging to a nation and supporting the actions of a nation are two entirely different things.