Laptop processors/GPUs are basically a thermal problem.
x86-64 (whatever the AMD one everyone is using now is named) carries architectural overhead, which has been overcome by simple market size/R&D budgets.
Desktop processors are basically a bandwidth to RAM problem.
Similar issues exist as in laptops, the 'same but different'.
In the 'long run' old architectures won't compete, it's not a railroad gauge analogy. Who knows what and when though.
Android has been poking it's nose into the laptop space.
It's really about tool sets. Once you buy into the 'webapp for everything' mentality. That is a big market, likely most of it. Everybody who can't keep their desktop OS running and uninfested to start.
Just wait for the malware to really start going. Always keep the write protect tab on your autonomous car. Watch out for teenagers showing you car's cameras videos with their phones.
Whatever happens, CPU is commodity. It's already commodity priced. Intel better get comfortable with ADM level margins. I don't think Apple would like the margins they find.
Back in the 80s 3M needed engineers and couldn't find anything in Minnesota. They spent a fortune, hired 100 CA engineers. By the end of the second winter only 1 was left. He was from there originally.
Depends. When you first buy the house, the Mortgage is usually more expensive. But inside 5 years it's typically less.
It does come down to how stable your life is. If you need to move in a year, the transaction costs of buying will kill your finances. But after 15-20 years, the mortgage is going to be half rent.
The toilet in the unfinished basement is common east of the Mississippi. It's so the low point of the plumbing is in the basement. Backups flood that rather than the kitchen/bathroom.
Your car will almost always pull a little anyhow, unless the road is perfectly flat or the car has terrible, numb, power steering where you can't feel anything.
There is no such thing as 'perfect' alignment. In the real world _everything_ is sloppy. Drive the car.
I own a 1960 that you have to 'saw on' the steering wheel, like in an old movie. It would be dangerous for a kid who didn't expect it or know how to handle it.
Recognize the treadmill. Learn something else, something somewhat durable. As much as possible 'on the clock'. Even if it means fucking up your current employers product. e.g. putting embedded SQL into the steaming piles of Javascript, like half digested corn. Writing web methods that expose the layer you want to learn, then putting your learning code into the 'framework'. You can find a way to justify it, they're clueless enough to be framework thrashing.
It's simply 'cookbook'* business. Overhead like accounting is overhead. Necessary and important, but ultimately a cost (just a lower cost/risk than the alternative).
* The same way other mature fields are derided as 'cookbook'. Civil is still complicated engineering, they just have a large library of proven methods And a 'standards' stick in an uncomfortable place, right where it belongs IMHO, don't really want (self described) 'creatives' designing bridges...That's how you end up with Javascript running on your server.
What's Kotlin? (Feminine hygiene? Geeks should'nt name products...)
I have far more than 10 years experience bullshiting experience I don't have. I first coded *, 12 years before it was specified.
That's what they're asking for when they ask for that. It's simply code for 'must be willing to sling bullshit'.
Avoid if at all possible, at least go in with eyes open. (Lehea) It will be a forest of shit trees, you supervisors will be shit birds. (/Lehea) But if very young and desperate, you can leverage it. You shouldn't have to go in on 'pure bullshit' more than once.
If you have to do it, learn from it. Not just technical, bullshit skills are lifelong useful. Who knows? You might end up a consultant.
On the backend, you get to deal with and code around bugs and idiosyncrasies of your database engine, business logic, object environment etc.
On the frontend, you get to deal with and code around bugs and idiosyncrasies of your supported browsers and devices, framework, other steaming piles of javascript etc.
If any of this shit worked as the theory said, it would be easy.
Anybody who starts grad school should understand the importance of their entire committee. If they go in blind and stupid, they have nobody to blame but themselves.
Outside science: Plenty of women, no fewer nutjobs and outsized egos. Hypothesis needs work.
Slashdot Mirror
To be fair. one day down isn't generally 'retooling' either. Even with planning and staging.
All the other old PhD jokes get 'funny'. This one always hits too close to home, gets 'Flamebait'
If anybody asks, I was coding in Kotlin in 1999.
I planned the death of many a teacher, some in great detail with my classmates. Nobody ever actually got hurt, but plans were made.
Assholes can't 'turn it off'. They live with an asshole every minute of every day, self punishing.
I only fap to dithered 16 color porn when I can't find ASCII line printer porn.
It's not hard to get to 100% of 'good enough'. But Apple won't like the margins in the CPU space.
Apple isn't after the servers or the gamers. Those spaces are where the last 10% might matter.
It's asymptotic. Each '50% there' takes 'half your resources', better find a resource stream.
Laptop processors/GPUs are basically a thermal problem.
x86-64 (whatever the AMD one everyone is using now is named) carries architectural overhead, which has been overcome by simple market size/R&D budgets.
Desktop processors are basically a bandwidth to RAM problem.
Similar issues exist as in laptops, the 'same but different'.
In the 'long run' old architectures won't compete, it's not a railroad gauge analogy. Who knows what and when though.
Android has been poking it's nose into the laptop space.
It's really about tool sets. Once you buy into the 'webapp for everything' mentality. That is a big market, likely most of it. Everybody who can't keep their desktop OS running and uninfested to start.
Just wait for the malware to really start going. Always keep the write protect tab on your autonomous car. Watch out for teenagers showing you car's cameras videos with their phones.
Whatever happens, CPU is commodity. It's already commodity priced. Intel better get comfortable with ADM level margins. I don't think Apple would like the margins they find.
PPC was a partnership. IIRC IBM, Motorola and Apple.
Apple isn't going to open a foundry.
I suspect someone had Intel shorted and used Bloomburg like the whores they are.
Isn't 'unified experience' what got us Windows 8?
Back in the 80s 3M needed engineers and couldn't find anything in Minnesota. They spent a fortune, hired 100 CA engineers. By the end of the second winter only 1 was left. He was from there originally.
Fuck the tundra. Fargo is a documentary.
Depends. When you first buy the house, the Mortgage is usually more expensive. But inside 5 years it's typically less.
It does come down to how stable your life is. If you need to move in a year, the transaction costs of buying will kill your finances. But after 15-20 years, the mortgage is going to be half rent.
Is this some new faction of furries?
In point of fact: SI valley formed because CA told bell labs to stuff their non-competes up their asses.
If was started by a group of defectors. If the new england states hadn't been kissing up to the big corporations of the day, it could have been there.
Old, often repeated, nonsense.
They excluded all benefits paid to individuals. CA has something like 30% of the nations government tit suckers.
As you say, my house is appreciating at a good rate. Why would I leave?
CA liberals _are_ annoying. But no worse then Holy rollers. I can ignore both.
The toilet in the unfinished basement is common east of the Mississippi. It's so the low point of the plumbing is in the basement. Backups flood that rather than the kitchen/bathroom.
Your car will almost always pull a little anyhow, unless the road is perfectly flat or the car has terrible, numb, power steering where you can't feel anything.
There is no such thing as 'perfect' alignment. In the real world _everything_ is sloppy. Drive the car.
I own a 1960 that you have to 'saw on' the steering wheel, like in an old movie. It would be dangerous for a kid who didn't expect it or know how to handle it.
At startup. Then load the data into memory in a Global named 'aLocalArray' and never access it again.
Recognize the treadmill. Learn something else, something somewhat durable. As much as possible 'on the clock'. Even if it means fucking up your current employers product. e.g. putting embedded SQL into the steaming piles of Javascript, like half digested corn. Writing web methods that expose the layer you want to learn, then putting your learning code into the 'framework'. You can find a way to justify it, they're clueless enough to be framework thrashing.
99.99% of IT has no 'secret sauce'.
It's simply 'cookbook'* business. Overhead like accounting is overhead. Necessary and important, but ultimately a cost (just a lower cost/risk than the alternative).
* The same way other mature fields are derided as 'cookbook'. Civil is still complicated engineering, they just have a large library of proven methods And a 'standards' stick in an uncomfortable place, right where it belongs IMHO, don't really want (self described) 'creatives' designing bridges...That's how you end up with Javascript running on your server.
What's Kotlin? (Feminine hygiene? Geeks should'nt name products...)
I have far more than 10 years experience bullshiting experience I don't have. I first coded *, 12 years before it was specified.
That's what they're asking for when they ask for that. It's simply code for 'must be willing to sling bullshit'.
Avoid if at all possible, at least go in with eyes open. (Lehea) It will be a forest of shit trees, you supervisors will be shit birds. (/Lehea) But if very young and desperate, you can leverage it. You shouldn't have to go in on 'pure bullshit' more than once.
If you have to do it, learn from it. Not just technical, bullshit skills are lifelong useful. Who knows? You might end up a consultant.
On the backend, you get to deal with and code around bugs and idiosyncrasies of your database engine, business logic, object environment etc.
On the frontend, you get to deal with and code around bugs and idiosyncrasies of your supported browsers and devices, framework, other steaming piles of javascript etc.
If any of this shit worked as the theory said, it would be easy.
Most roads are 'crowned', in part for drainage, but in part to make cars drift away from the center line.
If the GP is in England/Australia (or anyplace else where they drive on the wrong side) a slight pull to the right might be a problem.
Only if good to eat.
Otherwise don't revive it.
Anybody who starts grad school should understand the importance of their entire committee. If they go in blind and stupid, they have nobody to blame but themselves.
Outside science: Plenty of women, no fewer nutjobs and outsized egos. Hypothesis needs work.
Only lucrative degree seekers would get loans. Likely no loans at all for the first 2 years.
'Non-dischargeable' is the flip side of 'available'.
Not really a bad idea, but a non-starter politically. Implicit shutdown of half the nations liberal arts programs.