What about JavaFX? That at one time was the Next Best Thing, but (unlike Swing) has been dropped from the JDK. Where there are still Java desktop apps, has it managed to get any traction?
AdoptOpenJDK may be a better bet unless you want to update your JDK version every six months, or continue with an unpatched version. Oracle OpenJDK version 11 will only receive updates until version 12 is out. The commercial Oracle JDK version, being LTS, will receive them for a lot longer than that.
My understanding is that version 11 Oracle OpenJDK will have exactly the same patches applied as Oracle JDK (LTS), until version 12 comes out. Then the patches Oracle applies to Oracle JDK version 11 will not be applied to Oracle OpenJDK version 11. Oracle OpenJDK users will be expected to move to version 12. (This in turn will receive official Oracle patches until version 13 comes out, and so on. New versions are expected to come out every six months from now on.)
However, I believe some other JDK suppliers, like AdoptOpenJDK, will provide provide a patched version of version 11 even after version 12 is out.
Or do you mean that the binary requires and installer? If so that's just lazy and there's no excuse.
Yep, that's me, Lazy. Strangely I find don't need an excuse for being that!
Actually, I will get round to trying to install locally at some point. I think I compare it to Java or Go, where I can just download, extract, add one item to the $PATH environment variable, and then go.
Thanks. I did download the one for Linux before posting. Their being an 'install.sh' at the top level of the extracted archive promptly put me off! I would need to see what it does before I run it or try to work round it.
I do wonder how many whingeing about this are actually coders.
I too am interested in Rust and, indeed, any new language. I'm always curious to know which ones will thrive and which ones won't, and what the use-cases for each are, in other words, where would you use one rather than the other.
I'm not altogether sure of the relevance of 'SJW' is to this technically, especially as the term seems to be applied as a term of abuse (by others) rather than a term of self-identification (so in this case presumably used by those not involved in the development of the language).
I think my main objection so far to Rust is that I can't just download a tarball, unzip, set up some environment variables, and run. It seems that you have to run an installer, which I really dislike! But that's me.
1707 was the date of the acts of the union of the parliaments. There still remained (and still remains between these two) two legal systems; one for England and Wales, and one for Scotland. There is also a third one for Northern Ireland.
There are three separate prosecution services. One for England and Wales:
Over how many iterations? Perhaps after one year there will be a single-digit prevalence of patented seeds, but, assuming drift from the neighbour's farm occurs every year, what will this prevalence be after (say) ten years?
I'm using 16.04 LTS and will do the standard upgrade to 18.04 LTS once 18.04.1 comes out. I'll ignore 18.10 and wait until 20.04 LTS to upgrade again after that.
I'm not sure what a 'serious Linux user' is, but clearly I'm not one. However, "snap" sounds great with regards running new software on an old(ish) system without worrying too much about dependencies (or dependency conflict). Also, although I'm clearly not a 'serious Linux user', I think even I will be able to disable/remove any 'Amazon Integration' should I so wish. (And SystemD comes with Debian, and is not specifically an Ubuntu thing).
It's not quite that simple. As reported in the BBC:
US National Security Adviser John Bolton is reported as saying that European companies doing business with Iran will have to finish within six months or face US sanctions.
Apprenticeship is probably more associated with a trade or craft skill. I suppose these have traditionally been associated with 'blue collar' work, but not necessarily.
My company works in IT, and we have trained a number of apprentices over the years, most of whom did very well. This was more than just intern-ship - the training that they underwent was quite intensive and rigorous. But then, I've often thought of Software Development (for instance) as a craft skill.
As to white collar apprentices, wasn't there a US TV show called "The Apprentice"? (We had one here in the UK). I believe the original shows starred one of your more famous businessmen. I wonder whatever happened to him?
Thanks. I'll make a note of these (some I've heard mention before), and at some point I'm going to have a thorough read.
(I work mainly in support, so once I get exposure to a system, it's already written. However I do get curious as to how some of the stuff that we support actually get developed!)
Both may be convenient, but cash is a lot easier to budget with. All I need to do is look at my wallet to see how much I've got left of may allocated weekly spend!
I quite like it. I use it (to management) to describe our current role in Support. I find it helps to explain why, although we can generally support the whole stack, if they want something complex or difficult doing with a particular part of it, then need to bring a 'specialist'.
This though is a support thing, where we inherit the whole 'full stack' from the specialised Dev teams that developed the parts. For some reason the assumption is that whereas the Dev teams were specialised in specific areas, the Support team (us) can hit the ground running as experts in all aspects of the stack. A hackneyed phrase like this can explain why that is not necessarily the case.
(This is not to say that we're not experts. Our understanding and expertise *in some areas* exceeds that of any of the Dev teams. However, unlike most in the Dev teams, we still have to have a handle on the full stack.).
I would separate code writers from code debuggers.
Has this ever happened in a commercial environment? Just curious, as I've never come across the Job Description "Code Debugger". (well, not in my organisation). Yet, thinking about it, (and having looking at a lot of code from a support perspective) I can see the need!
Really what it sounds like is a refactoring team. Unfortunately it sounds like what "management" would call an "unnecessary overhead".
The poor people who suffer are those left in the support teams. (Which is where I seem to have spent most of my career recently. Unfortunately it seems I'm good at it). KISS would make my life a lot easier, especially with regards frameworks. I've come to the conclusion that these are far too overused, and when they 'go wrong' (which they tend to do, being both complex and brittle), they can be a pain to sort out.
In my experience the people who need to know the "full stack" are the Support team, not the Dev teams. The Dev teams can be split (front-end, back-end, middle-ware for instance), but all these get 'merged' when handing over to Support (which has its own set of skill-sets).
Slashdot Mirror
What about JavaFX? That at one time was the Next Best Thing, but (unlike Swing) has been dropped from the JDK. Where there are still Java desktop apps, has it managed to get any traction?
AdoptOpenJDK may be a better bet unless you want to update your JDK version every six months, or continue with an unpatched version. Oracle OpenJDK version 11 will only receive updates until version 12 is out. The commercial Oracle JDK version, being LTS, will receive them for a lot longer than that.
My understanding is that version 11 Oracle OpenJDK will have exactly the same patches applied as Oracle JDK (LTS), until version 12 comes out. Then the patches Oracle applies to Oracle JDK version 11 will not be applied to Oracle OpenJDK version 11. Oracle OpenJDK users will be expected to move to version 12. (This in turn will receive official Oracle patches until version 13 comes out, and so on. New versions are expected to come out every six months from now on.)
However, I believe some other JDK suppliers, like AdoptOpenJDK, will provide provide a patched version of version 11 even after version 12 is out.
Yes, I will run it locally. I'm sure it will complain if it can't install locally.
Or do you mean that the binary requires and installer? If so that's just lazy and there's no excuse.
Yep, that's me, Lazy. Strangely I find don't need an excuse for being that!
Actually, I will get round to trying to install locally at some point. I think I compare it to Java or Go, where I can just download, extract, add one item to the $PATH environment variable, and then go.
Thanks. I did download the one for Linux before posting. Their being an 'install.sh' at the top level of the extracted archive promptly put me off! I would need to see what it does before I run it or try to work round it.
I do wonder how many whingeing about this are actually coders.
I too am interested in Rust and, indeed, any new language. I'm always curious to know which ones will thrive and which ones won't, and what the use-cases for each are, in other words, where would you use one rather than the other.
I'm not altogether sure of the relevance of 'SJW' is to this technically, especially as the term seems to be applied as a term of abuse (by others) rather than a term of self-identification (so in this case presumably used by those not involved in the development of the language).
I think my main objection so far to Rust is that I can't just download a tarball, unzip, set up some environment variables, and run. It seems that you have to run an installer, which I really dislike! But that's me.
I'm not sure what https://duck.co/ is, but I am quite sure it's not the same as https://duckduckgo.com/
what's the point?
I can't help thinking all these have somewhat the same answer!
Oh, and found this;
Lack of health insurance and U.S. mortality
and an older article;
New study finds 45,000 deaths annually linked to lack of health coverage
How is this better than the 'socialised' system we have in the UK?
Both moms were brought to the U.S. right away for treatment even though it wasn't "free".
Just curious, but how long would they have waited if they lived in the US and (1) had no insurance and (2) couldn't afford to pay?
1707 was the date of the acts of the union of the parliaments. There still remained (and still remains between these two) two legal systems; one for England and Wales, and one for Scotland. There is also a third one for Northern Ireland.
There are three separate prosecution services. One for England and Wales:
The Crown Prosecution Service
One for Scotland:
The Crown Office and Procurator Fiscal Service
And one for Northern Ireland:
About the PPS
For some differences between England and Scotland: The Differences Between The English And Scottish Law
Northern Ireland is different again. (It is the only part of the United Kingdom where abortion is still illegal.)
As to which of these the US got its laws from, I'll leave that to someone in the US!
Over how many iterations? Perhaps after one year there will be a single-digit prevalence of patented seeds, but, assuming drift from the neighbour's farm occurs every year, what will this prevalence be after (say) ten years?
I'm using 16.04 LTS and will do the standard upgrade to 18.04 LTS once 18.04.1 comes out. I'll ignore 18.10 and wait until 20.04 LTS to upgrade again after that.
I'm not sure what a 'serious Linux user' is, but clearly I'm not one. However, "snap" sounds great with regards running new software on an old(ish) system without worrying too much about dependencies (or dependency conflict). Also, although I'm clearly not a 'serious Linux user', I think even I will be able to disable/remove any 'Amazon Integration' should I so wish. (And SystemD comes with Debian, and is not specifically an Ubuntu thing).
US National Security Adviser John Bolton is reported as saying that European companies doing business with Iran will have to finish within six months or face US sanctions.
Iran nuclear deal: Powers seek to save agreement after US exit
You didn't get Dennis Ritchie issuing edicts about holding doors open for old folks and not kicking dogs, did you?
I would imagine that Dennis Richie never encountered a situation where he had to ask people to:
Maybe back in the day, this was how everyone behaved, without needing to be prompted. Nowadays, of course...
Apprenticeship is probably more associated with a trade or craft skill. I suppose these have traditionally been associated with 'blue collar' work, but not necessarily.
My company works in IT, and we have trained a number of apprentices over the years, most of whom did very well. This was more than just intern-ship - the training that they underwent was quite intensive and rigorous. But then, I've often thought of Software Development (for instance) as a craft skill.
As to white collar apprentices, wasn't there a US TV show called "The Apprentice"? (We had one here in the UK). I believe the original shows starred one of your more famous businessmen. I wonder whatever happened to him?
Thanks. I'll make a note of these (some I've heard mention before), and at some point I'm going to have a thorough read.
(I work mainly in support, so once I get exposure to a system, it's already written. However I do get curious as to how some of the stuff that we support actually get developed!)
Both may be convenient, but cash is a lot easier to budget with. All I need to do is look at my wallet to see how much I've got left of may allocated weekly spend!
You'll be pleased to hear that I've got no plans to come over and steal your job.
I quite like it. I use it (to management) to describe our current role in Support. I find it helps to explain why, although we can generally support the whole stack, if they want something complex or difficult doing with a particular part of it, then need to bring a 'specialist'.
This though is a support thing, where we inherit the whole 'full stack' from the specialised Dev teams that developed the parts. For some reason the assumption is that whereas the Dev teams were specialised in specific areas, the Support team (us) can hit the ground running as experts in all aspects of the stack. A hackneyed phrase like this can explain why that is not necessarily the case.
(This is not to say that we're not experts. Our understanding and expertise *in some areas* exceeds that of any of the Dev teams. However, unlike most in the Dev teams, we still have to have a handle on the full stack.).
Except for one item that is needed, but which can be quite volatile, so a full stack restart is required when it changes.
I would separate code writers from code debuggers.
Has this ever happened in a commercial environment? Just curious, as I've never come across the Job Description "Code Debugger". (well, not in my organisation). Yet, thinking about it, (and having looking at a lot of code from a support perspective) I can see the need!
Really what it sounds like is a refactoring team. Unfortunately it sounds like what "management" would call an "unnecessary overhead".
The poor people who suffer are those left in the support teams. (Which is where I seem to have spent most of my career recently. Unfortunately it seems I'm good at it). KISS would make my life a lot easier, especially with regards frameworks. I've come to the conclusion that these are far too overused, and when they 'go wrong' (which they tend to do, being both complex and brittle), they can be a pain to sort out.
In my experience the people who need to know the "full stack" are the Support team, not the Dev teams. The Dev teams can be split (front-end, back-end, middle-ware for instance), but all these get 'merged' when handing over to Support (which has its own set of skill-sets).