Well, surprise, the @goto macro has oddball limitations, never mind the ugly punctuation. Just give me a real goto without the awkward half measure please, thanks.
It does have compound types and extensible types (subtypes). Instead of class methods it has parametric polymorphism, a flavor of generics somewhat resembling interfaces. While this seems nice and natural as far as it goes, I am not sure how far it goes. Jury is out.
I absolutely hate the case conventions for identifiers. Why does every language of the month need to come with at least one blatantly stupid, avoidable idiocy guaranteed to trigger a large proportion of its intended audience? This is a minor thing but not something I could ever used to. A prime candidate for "sorry that was dumb, let's just fix it now before it festers".
At least, no significant indents, thanks for that.
Good or bad? Hard to say, but I would rather have these things than not. It is currently the fashion to leave out classes and provide similar functionality with interfaces or equivalent, but I find that a sticking point. Let's see how it goes.
There are situations where goto is far preferable to fiddling with local logic variables and such. Sure, goto can be tricky to implement with respect to local scope and such, but leaving it out to avoid work... doubtful. Leaving out goto for purity reasons... beyond doubtful.
My first impression of Julia was favorable. I fired up the command line interpreter and typed in 2 + 2. Prints out 4, just like Python. Then typed in 2**4:
julia> 2**4 ERROR: syntax: use "^" instead of "**"
Wow, I like that. I managed to define a function, f(n) = n * n, without reading the manual but didn't get much further without reading the docs docs. But great start, I already see this as a reasonable alternative to what I usually use Python for: a desktop calculator.
Initial impression matters. Now, with a postive one, I will go deeper and see if Julia is really what I should be coding one-offs in, instead of Python or Go.
Didn't RTFM? Julia has several backends including LLVM. Performance is more than respectable. In particular, puts Python to shame and close to Java + JIT but without the JIT lag, load time and memory footprint annoyance.
It does take more time to install if the laptop was preinstalled with Windows. It's Windows: 0, Linux 0 + n. If the hard drive dies we'll revisit - that's how one of my other PCs went from 8 -> 7.
You configure the bios to boot from USB first, you're going to fiddle with bios settings anyway, so Linux 1, Windows 1. You boot from USB. You're going to boot anyway, so Linux 1 Window 1. You answer a few questions the go do something else for an hour while the packages download over the net. It installs itself in just a few minutes because it's a flash disk. Linux 1, Windows 0. Windows updates itself when you boot, making itself unusable. Linux 0, Windows 1. Patch Tuesday arrives and Windows is now ahead of Linux in downtime. There is only one install but there are many Patch Tuesdays, so Linux wins on not wasting your time. You know this.
Then after that, Microsoft spies on you, Linux does not, unless you explicitly enroll for package popularity, in which case it respectfully stays away from all your data except package installs. Windows is just plain nasty. You know this.
IIRC, the main issue driving FilmGimp/CinePaint was lack of 16 bit per color precision. When Gimp finally got that merged (and a bunch of other precisions up to 32 bit float per color) there was no longer a need to continue developing CinePaint.
Though I somewhat mired in ARM processor alphabet soup here, it looks to me like the new processor is a 64 bit V8 processor compared to the Gear's 32 bit A9, so it is a much beefier processor. To come in at about the same battery life is worthy of note. I am pretty sure that the new Exynos 9110 has considerably higher IPC and cache that the Gear's Exynos 4212. The process shrink to 10nm made that battery life possible.
Enlightenment lives long and prospers. Never mind how idiotic it is to abuse C like that. It works, because one alpha hacker camped out at Samsung HQ stuck with it and made it work.
The sky is falling, cried Chicken Little. But it was really just an acorn, and the sky did not fall. The PC industry went on for two decades before it finally got boring enough to knock PCMag off the shelves and put Comdex out of business. The Smartphone industry has another decade to go. The auto industry announces each new year of each model like clockwork, and somebody laps that up. I can't say I never did.
I, for one, do want to know about how this year's phone does more on less battery, or actually thinks for itself, or has some wizbang new functionality I am supposed to be unable to live without or whatever, so keep em coming thanks.
I'm not really arguing your points, but for me it's just not worth the time.
Not really arguing your points either, they are a matter of your perception. However "worth the time"... what time? You make it sound like Linux takes more time than Windows, which isn't true. Maybe a long time ago it was, not sure about that, but today the time you save by not having any such thing as "Patch Tuesday", by itself, tips the balance in favor of Linux. Not to mention, the machine starts faster, runs raster, never crashes... time is money.
I Googled it for shits and giggles and it's the usual thing - some people saying it works and other people complaining about Wifi or some other peripheral.
Well you are much too smart for that, you would Google to make sure existing users report that all important functionality is supported. I on the other hand, am not that smart, these days I just go ahead and do it and fix what breaks. Usually nothing. The last three laptops in a row everything worked perfectly. Keep in mind that people only post if something breaks, not if it works perfectly.
More often than not I install onto a laptop that was bought to run Windows and just gathered dust after a brief flurry of use. People don't use laptops much these days, you see. You browse on your phone and the rest is mainly school or biztrips. Remember when everybody on the train had a laptop bag? Bygone days.
I don't bother with dual boot any more, I just pull out the Windows disk and put in a nicer one for the Linux install. I put aside the original disk, thinking that I might need to run Windows sometime. But that never happens, in every case I eventually just formatted the Windows disk and put it back to use. I suppose I could just image the disk onto a big HDD to run under KVM if I cared, maybe I will do that next time.
If you are having wifi troubles with Linux, chances are it's Atheros. This has been a solved issue for some time, but you need to load the firmware. If you don't, it kinda works, but disconnects a lot. I struggled with that a bit myself with a USB wifi dongle that I distinctly remember working in the past with Ubuntu. That is because Ubuntu automatically installed a binary driver for it. Debian doesn't hold your hand on that, I needed to look in the kernel log to see what was breaking.
I wouldn't try to install Linux on a brand-new laptop, either, unless I knew all the features were supported.
Right, I usually google to check that somebody else is already running Linux on it. But not always. A Wintel PC generally just works these days, including power management, video, etc. Sometimes you need to wait for somebody to post drivers for things like oddball special keys. On the whole, Linux hardware support makes Windows look really lame now.
It's main proposed purpose is to protect the US (and it's allies) from space based attacks which are not primarily of a physical nature but more technological.
You're being too charitable to Trump, who genuinely believes it's to fight the spiders from Mars with ray guns.
I will, because time is money. In fact that's just the parts cost these days since I got into my own builds. Next build will be $2000 parts cost because it will be a top of the line Threadripper 2. You could even go crazy and do an overclocked 64 core (upcoming) Epyc on EATX but that's where I draw the line. No problem at all with dropping $2K on a box that delivers the value.
A phone is a different story: what is exactly is the payback for the flagship tax, particularly knowing that this year's flagship is next year's also ran?
Not really. It is just not very important to get a new Android release on day one, in fact as with any OS it makes a whole lot more sense to git it a couple more months and get the.1 release. I for one don't take any marks off at all for going back one release on a flagship to give the developers a bit more time to work out the wrinkles. Quite the contrary.
Your fashion analogy is really just the opposite of what's happening here.
Well, surprise, the @goto macro has oddball limitations, never mind the ugly punctuation. Just give me a real goto without the awkward half measure please, thanks.
Julia has a goto macro, I like the idea but have not yet tried it. If it works (I don't see why it should not) then nice solution.
Classes are definitely included in the language.
Julia has no classes
It does have compound types and extensible types (subtypes). Instead of class methods it has parametric polymorphism, a flavor of generics somewhat resembling interfaces. While this seems nice and natural as far as it goes, I am not sure how far it goes. Jury is out.
I absolutely hate the case conventions for identifiers. Why does every language of the month need to come with at least one blatantly stupid, avoidable idiocy guaranteed to trigger a large proportion of its intended audience? This is a minor thing but not something I could ever used to. A prime candidate for "sorry that was dumb, let's just fix it now before it festers".
At least, no significant indents, thanks for that.
Here, take these handcuffs.
Good or bad? Hard to say, but I would rather have these things than not. It is currently the fashion to leave out classes and provide similar functionality with interfaces or equivalent, but I find that a sticking point. Let's see how it goes.
There are situations where goto is far preferable to fiddling with local logic variables and such. Sure, goto can be tricky to implement with respect to local scope and such, but leaving it out to avoid work... doubtful. Leaving out goto for purity reasons... beyond doubtful.
Cheat sheet
I think that's called a "specializing compiler", like Psco/PyPy but not JIT. I don't juch like JITs, actually. A good fit for LISP but not much else.
My first impression of Julia was favorable. I fired up the command line interpreter and typed in 2 + 2. Prints out 4, just like Python. Then typed in 2**4:
Wow, I like that. I managed to define a function, f(n) = n * n, without reading the manual but didn't get much further without reading the docs docs. But great start, I already see this as a reasonable alternative to what I usually use Python for: a desktop calculator.
Initial impression matters. Now, with a postive one, I will go deeper and see if Julia is really what I should be coding one-offs in, instead of Python or Go.
Didn't RTFM? Julia has several backends including LLVM. Performance is more than respectable. In particular, puts Python to shame and close to Java + JIT but without the JIT lag, load time and memory footprint annoyance.
I am wondering if they have a Code of Conduct for the language?
This language is polite and respectful.
It does take more time to install if the laptop was preinstalled with Windows. It's Windows: 0, Linux 0 + n. If the hard drive dies we'll revisit - that's how one of my other PCs went from 8 -> 7.
You configure the bios to boot from USB first, you're going to fiddle with bios settings anyway, so Linux 1, Windows 1. You boot from USB. You're going to boot anyway, so Linux 1 Window 1. You answer a few questions the go do something else for an hour while the packages download over the net. It installs itself in just a few minutes because it's a flash disk. Linux 1, Windows 0. Windows updates itself when you boot, making itself unusable. Linux 0, Windows 1. Patch Tuesday arrives and Windows is now ahead of Linux in downtime. There is only one install but there are many Patch Tuesdays, so Linux wins on not wasting your time. You know this.
Then after that, Microsoft spies on you, Linux does not, unless you explicitly enroll for package popularity, in which case it respectfully stays away from all your data except package installs. Windows is just plain nasty. You know this.
Linux doesn't just own the render farms. many or most of the workstations are Linux too. A lot of Maya. Why? More stable, more throughput.
It is common knowledge that the man of whom you speak is a poser with no traction whatsover in the community.
Obvious troll is obvious. "Two decades", sure buddy.
IIRC, the main issue driving FilmGimp/CinePaint was lack of 16 bit per color precision. When Gimp finally got that merged (and a bunch of other precisions up to 32 bit float per color) there was no longer a need to continue developing CinePaint.
Though I somewhat mired in ARM processor alphabet soup here, it looks to me like the new processor is a 64 bit V8 processor compared to the Gear's 32 bit A9, so it is a much beefier processor. To come in at about the same battery life is worthy of note. I am pretty sure that the new Exynos 9110 has considerably higher IPC and cache that the Gear's Exynos 4212. The process shrink to 10nm made that battery life possible.
Enlightenment lives long and prospers. Never mind how idiotic it is to abuse C like that. It works, because one alpha hacker camped out at Samsung HQ stuck with it and made it work.
The sky is falling, cried Chicken Little. But it was really just an acorn, and the sky did not fall. The PC industry went on for two decades before it finally got boring enough to knock PCMag off the shelves and put Comdex out of business. The Smartphone industry has another decade to go. The auto industry announces each new year of each model like clockwork, and somebody laps that up. I can't say I never did.
I, for one, do want to know about how this year's phone does more on less battery, or actually thinks for itself, or has some wizbang new functionality I am supposed to be unable to live without or whatever, so keep em coming thanks.
Can you say clickbait.
They were students. Now they are Google employees.
Good luck, you will need it.
I'm not really arguing your points, but for me it's just not worth the time.
Not really arguing your points either, they are a matter of your perception. However "worth the time"... what time? You make it sound like Linux takes more time than Windows, which isn't true. Maybe a long time ago it was, not sure about that, but today the time you save by not having any such thing as "Patch Tuesday", by itself, tips the balance in favor of Linux. Not to mention, the machine starts faster, runs raster, never crashes... time is money.
I Googled it for shits and giggles and it's the usual thing - some people saying it works and other people complaining about Wifi or some other peripheral.
Well you are much too smart for that, you would Google to make sure existing users report that all important functionality is supported. I on the other hand, am not that smart, these days I just go ahead and do it and fix what breaks. Usually nothing. The last three laptops in a row everything worked perfectly. Keep in mind that people only post if something breaks, not if it works perfectly.
More often than not I install onto a laptop that was bought to run Windows and just gathered dust after a brief flurry of use. People don't use laptops much these days, you see. You browse on your phone and the rest is mainly school or biztrips. Remember when everybody on the train had a laptop bag? Bygone days.
I don't bother with dual boot any more, I just pull out the Windows disk and put in a nicer one for the Linux install. I put aside the original disk, thinking that I might need to run Windows sometime. But that never happens, in every case I eventually just formatted the Windows disk and put it back to use. I suppose I could just image the disk onto a big HDD to run under KVM if I cared, maybe I will do that next time.
If you are having wifi troubles with Linux, chances are it's Atheros. This has been a solved issue for some time, but you need to load the firmware. If you don't, it kinda works, but disconnects a lot. I struggled with that a bit myself with a USB wifi dongle that I distinctly remember working in the past with Ubuntu. That is because Ubuntu automatically installed a binary driver for it. Debian doesn't hold your hand on that, I needed to look in the kernel log to see what was breaking.
I wouldn't try to install Linux on a brand-new laptop, either, unless I knew all the features were supported.
Right, I usually google to check that somebody else is already running Linux on it. But not always. A Wintel PC generally just works these days, including power management, video, etc. Sometimes you need to wait for somebody to post drivers for things like oddball special keys. On the whole, Linux hardware support makes Windows look really lame now.
It's main proposed purpose is to protect the US (and it's allies) from space based attacks which are not primarily of a physical nature but more technological.
You're being too charitable to Trump, who genuinely believes it's to fight the spiders from Mars with ray guns.
I won't even buy a desktop computer for $1000.
I will, because time is money. In fact that's just the parts cost these days since I got into my own builds. Next build will be $2000 parts cost because it will be a top of the line Threadripper 2. You could even go crazy and do an overclocked 64 core (upcoming) Epyc on EATX but that's where I draw the line. No problem at all with dropping $2K on a box that delivers the value.
A phone is a different story: what is exactly is the payback for the flagship tax, particularly knowing that this year's flagship is next year's also ran?
Not really. It is just not very important to get a new Android release on day one, in fact as with any OS it makes a whole lot more sense to git it a couple more months and get the .1 release. I for one don't take any marks off at all for going back one release on a flagship to give the developers a bit more time to work out the wrinkles. Quite the contrary.
Your fashion analogy is really just the opposite of what's happening here.