One of the problems with C is that it gives bad programmers enough rope to hang themselves, and anyone else nearby. It also allows any programmer who was careless at 5pm on a Friday that much rope, or one who assumed a library was secure and correct
C is fast, but the issues outlined above mean that failure has a large number of entry points, which makes it harder for processes (code review and various levels of testing) to police issues. With a language that is safer by design then provided the compilation process is dependable, it should be safer, and the compilation process should be more tested through use.
Languages that are safer by design are no panacea, and there can be issues with efficiency of the code, though. And even with that, formal proof that the code encodes the specification is rarely done.
Even with code that is correct, the specification (if it even formally exists) may not be, and modern systems are made from numerous components, and the architecture may be incorrect.
I'd agree with the siblings that recruiters tend to require significant AND recent experience in the particular programming language asked for. For example, I was once told that because I hadn't used a particular language professionally for two years, then they considered me to not be appointable, despite 15 years of previous experience with it. Adaptability doesn't seem to be valued. Mind you, they also wanted to give them a timescale for a project despite me indicating that a short feasibility study would be required, and that to ask for a breakdown with insufficient information was unreasonable.
It's what did I lock the door I should really go to bed where's the cat what bread should I get tomorrow where did I put my phone why isn't whelmed a word whatever happened to Limahl I thought too.
In 2002-3 the fear in western nations was deflation and then the potential for a depression. Greenspan avoided that, but the can was only kicked as far as 2007. Hopefully the can is no longer in play.
Obama took office in January 2009, the recession ended at the end of June 2009. That's not eighteen months. The ENTIRE recession was eighteen months, which might be the figure you are confusing it with.
Fast is good, but it could be fast and less ugly. I'd accept some CSS and a few images, but it would be nice to avoid fetching half the world's entire Javascript code base like some websites seem to do. I would think there is some middle ground between pretty and fast GNU could use. Some structural changes would be good too, but it's certainly not the worst structured site I've seen.
If there is not enough resource a human should be looking at that system, not just restarting a daemon
Ideally, yes. Sometimes scale or staff availability makes that difficult, though. But it might lead to instability without analysis. Whether that is acceptable depends on the business's risk appetite and risk management processes, although analysing the risk can be non-trivial, especially in complex architectures that can, more-of-less, exhibit emergent behaviour.
So the Chinese are basically IKEA... They clone more expensive furniture, mass produce it out of cheap materials and massively undercut the master craftsmen who built the originals.
I don't think the master craftsmen made flat packs, on the whole. Well, unless they were building cathedral roofs, which were often prefabricated on the ground, but I don't think IKEA sells a 'Snot' flat pack cathedral as yet.
Are you serious? From Eurostat: "Among the EU's trading partners, China was the largest partner for EU imports, and the second largest partner for EU exports in 2016.". Imports are just shy of 350b Euros per annum.
The issue is not necessarily the daemon that is failing using the resource, but potentially some other process. So daemon quits, resources freed, other process uses the resources.
However, not all OSes free all resources on all crashes.
Yes, resource starvation is definitely a time you'd not want a restart, unless it's a case of something like a lack of licences served by FlexLM, but you wouldn't really want to design a system with a daemon depending on an externally served licence that is pooled with other consumers of that licence type.
Running a business takes a different set of skills to being developer, so expecting people to just start their own business is unrealistic. Also, many small businesses fail. Thus, it can be an entirely rational decision to be an employee. It might be nice to see more co-ops to provide some of the ownership, but with economies of scale.
Slashdot Mirror
Not agile enough?
Forward facing flashing blue lights are illegal in every state.
Law-abiding criminals won't use them, then.
They might want to rename the divisions too, as birds not being descended from the bird-hipped group looks somewhat silly now.
But when all the other dinosaurs died, what would they eat? Oh, yeah, fish. Never mind.
Crocs are also much less likely to be adversely affected by the poisonous plants they don't eat.
To my mind, the state machine should come first, as part of the design, and then it should be implemented, not the reverse.
One of the problems with C is that it gives bad programmers enough rope to hang themselves, and anyone else nearby. It also allows any programmer who was careless at 5pm on a Friday that much rope, or one who assumed a library was secure and correct C is fast, but the issues outlined above mean that failure has a large number of entry points, which makes it harder for processes (code review and various levels of testing) to police issues. With a language that is safer by design then provided the compilation process is dependable, it should be safer, and the compilation process should be more tested through use. Languages that are safer by design are no panacea, and there can be issues with efficiency of the code, though. And even with that, formal proof that the code encodes the specification is rarely done. Even with code that is correct, the specification (if it even formally exists) may not be, and modern systems are made from numerous components, and the architecture may be incorrect.
I'd agree with the siblings that recruiters tend to require significant AND recent experience in the particular programming language asked for. For example, I was once told that because I hadn't used a particular language professionally for two years, then they considered me to not be appointable, despite 15 years of previous experience with it. Adaptability doesn't seem to be valued. Mind you, they also wanted to give them a timescale for a project despite me indicating that a short feasibility study would be required, and that to ask for a breakdown with insufficient information was unreasonable.
They didn't do much prove it as quantify it. In any case common sense (e.g. cold causes colds) is often wrong.
Are there non-linear feet?
Composting public toilets would make more sense, given the economies of scale. Unless they become like music festival toilets... Eww.
It's what did I lock the door I should really go to bed where's the cat what bread should I get tomorrow where did I put my phone why isn't whelmed a word whatever happened to Limahl I thought too.
In 2002-3 the fear in western nations was deflation and then the potential for a depression. Greenspan avoided that, but the can was only kicked as far as 2007. Hopefully the can is no longer in play.
Obama took office in January 2009, the recession ended at the end of June 2009. That's not eighteen months. The ENTIRE recession was eighteen months, which might be the figure you are confusing it with.
It worked for Iceland as it's a small nation with a particular financial sector with respect to external financial assets. Not an option for most
The UK used to, until the 90s, have blasphemy laws, although they were not enforced. I don't see any move towards new blasphemy laws.
Many European countries have been very open to immigration, especially from their former colonies, and in the case of Germany, Turkey.
Fast is good, but it could be fast and less ugly. I'd accept some CSS and a few images, but it would be nice to avoid fetching half the world's entire Javascript code base like some websites seem to do. I would think there is some middle ground between pretty and fast GNU could use. Some structural changes would be good too, but it's certainly not the worst structured site I've seen.
If there is not enough resource a human should be looking at that system, not just restarting a daemon
Ideally, yes. Sometimes scale or staff availability makes that difficult, though. But it might lead to instability without analysis. Whether that is acceptable depends on the business's risk appetite and risk management processes, although analysing the risk can be non-trivial, especially in complex architectures that can, more-of-less, exhibit emergent behaviour.
So the Chinese are basically IKEA... They clone more expensive furniture, mass produce it out of cheap materials and massively undercut the master craftsmen who built the originals.
I don't think the master craftsmen made flat packs, on the whole. Well, unless they were building cathedral roofs, which were often prefabricated on the ground, but I don't think IKEA sells a 'Snot' flat pack cathedral as yet.
The EU does not import much from China ...
Are you serious? From Eurostat: "Among the EU's trading partners, China was the largest partner for EU imports, and the second largest partner for EU exports in 2016.". Imports are just shy of 350b Euros per annum.
As an aside: If you have a fool-proof way of doing this, please let me know.
I do, but this margin is not sufficiently large to contain the method.
The issue is not necessarily the daemon that is failing using the resource, but potentially some other process. So daemon quits, resources freed, other process uses the resources.
However, not all OSes free all resources on all crashes.
Yes, resource starvation is definitely a time you'd not want a restart, unless it's a case of something like a lack of licences served by FlexLM, but you wouldn't really want to design a system with a daemon depending on an externally served licence that is pooled with other consumers of that licence type.
Running a business takes a different set of skills to being developer, so expecting people to just start their own business is unrealistic. Also, many small businesses fail. Thus, it can be an entirely rational decision to be an employee. It might be nice to see more co-ops to provide some of the ownership, but with economies of scale.