Posts by Dagg 815 publicly visible posts • joined 13 Jul 2010
Actually you are wrong it is defiantly not the doctors.
When I had a car accident in the US I asked the nurse "what the hell is going on?" her comment was "are you a kiwi?" "Yes", she said "same here, they are NOT trying to cure you, they are just making sure you can't sue them!"
And she "said it was the insurance companies that determined what treatment could be paid for"
So you are wrong.
Safe rust code does not have memory safety bugs, because it can’t.
So what does it do if I try to write to array entry 101 when the array only has 100 entries?
Prevent the write and continue
Crash the program
What? Because in both those cases the result is not good in a production system.
Shirley you must be kidding. As the saying goes you can choose your friends you can't choose your family.
I've seen many an xmas lunch where by half way through the afternoon one half of the "family" was ready to kill the other half. I've seen my wife have a punch on with her younger sister. The sisters partner and me both stayed right out.
Albanese : “…sending a message…” - usual weasel words when he already knows it is not going to work.
Actually it was Dutton that originally came up with under 16 laws and Albanese could see that any attempt to stop them would fail. That is why it passed as both major parties agreed on it.
So what exactly does it do in Rust, and how is that safe?
That is actually a serous question. What actually does happen?
* Does the whole program crash immediately?
* Does it throw an exception?
* Does it just block the access and blindly continue?
The answer to this is extremely important in a production system. And the impact of the resolution will cause an issue depending on the function of the actual package.
* Game
* Word processor
* Banking
* EFTPOS
* Retail POS
* Realtime - industrial process control
* Realtime - nuclear reactor
* Realtime - fire control platform
* etc
So will someone who know rust please indicate how it will respond?
So... the problem is if there is an error in the source code it will just be transferred into the destination code. it's just GIGO
To actually fix any potential memory errors will require extensive refactoring. This will require access to the original high level/business requirements that were used to create the original code. You will also require ALL of the subsequent change requests and process changes.
And then you will need to try to track down the wildcard changes that you cannot find any reason as to why they were made.
Should be justifiable homicide to kill morning people!
I've worked for a few bosses that insisted the office started early and then berated me because I had a BAD attitude. I used to work for IBM(bastards) and they loved so called breakfast briefings and breakfast meetings. These were always arranged to occur before work hours so they were getting your time for free. They used to justify this by saying look we give you free food. Bastards...
In Britain it's called summer time
Nah, can't be correct. I've lived in Britain and I can remember summers that never occurred. The weather was just cold, wet and cloudy and they still had daylight saving. For those non summers they should have cancelled the "summer time" or at least asked for the money back!
I used to look after a server which collected data from different time zones. The whole DST issue was a nightmare. In the end all data was stored with UTC timestamps.
Major issue in Australia with each state having its own timezone and only the southern states having daylight saving. In some cases parts (far west of NSW) of one state adopt the timezone of next door state.
So not only do you need to store datetime in UTC you also need to store the native offset from UTC.
I'd much rather go to work in the dark than come home from work in the dark.
Don't know where you are in the UK, but I was in the midlands and mid winter it was drive to work in the dark, see the sun barely rise above the horizon mid morning the set mid afternoon then drive home in the dark.
I'm now living in Australia and the southern states have daylight saving and it is a waste of time, The state of Victoria maps to North Africa in the northern hemisphere and daylight saving is a complete waste of time.
Why not build the data centres next to a large hydro or geothermal generation system. They did that in the south of New Zealand for an aluminium smelter when New Zealand had no aluminium ore or any need to use large quantities of aluminium. What it did have was large quantities of cheap electricity generated by hydro power.
These data centres don't need to be located in the middle of a city, all the need is a high speed fibre link to the rest of the world. Geothermal generation in Iceland...
The SMR are all well and good, but what about the cost! I have not seen any valid numbers from anyone. Maybe someone from El reg can provide a Cost Benefit Analysis for an SMR covering construction, operation and disposal?
The Australian conservative opposition (the coalition) have been pushing these as a low carbon solution. The issue is they can't/won't provide costings.
They also cannot get any private companies to commit to building them so they when they get into power they (a conservative government) will build them.
A couple of things stand out.
1/ If these are that good/great and will make money why aren't the private sector interested?
2/ And why would a conservative government that like small government and privatise everything suddenly what to commit to spending money on public infrastructure.
The only answer is that the SMRs are a non starter because they will never be financially viable, hence no private interest and it means the the coalition can say oops we tried and then keep their promise to the fossil fuel industry to keep burning coal and gas.
The only original reason for a double entry system is you only needed to add, no subtraction was required. From what I remember this was to do with the use of roman numerals.
In sales/ledger/account systems you don't need a double ledger but each transaction is recorded against each sale/purchase/banking etc.
Post office terminal sent a sales transaction to head office. Head office sent an ack packet back. Ack packet didn’t arrive at the terminal. Terminal retransmitted the transaction. Head office logged it as a second sale.
WTF!!! This is the classic double commit problem. I remember being taught all about this in compsci and working with it in EFTPOS using AS2805/ISO8583.
The standard approach was to send a request and if the response did not arrive in time a reversal was sent. The original requests and responses could be discarded but the reversals had to be stored and forwarded. Total F*ckwits
I hope Linux Mint will start advertising to entice Windows users to install Mint
Tried it and reverted back as the only thing that worked as before was Firefox. Tried wine and the stuff I could get to run sort of ran but was slow and strange display artifacts. Things like a hidden dialog box rectangle that locked a part of the screen.
If it doesn't have drivers because the H/W's too new
Wrong, the hardware is about 3 years old but has never been supported under linux. It is under Windows and Mac. Or in the case of a printer it will sort of works under linux but you are not able to head clean or head align.
And you can always try running your irreplaceable Windows app under Windows of your choice in an isolated VM for safety.
Tried it and instead of being able to fully use the features of both screens together you get a little window. And runs so slow.
I'm not the one beefing about windows. I just get pissed off with the attitude that linux will fix everything, linux is the solution, linux is mother, linux is father...
I will and I want to change to linux ASAP once it is able to deliver what I need and solve the problems that I have.
uses pointers or indexes into arrays may well fail to compile
At least the suspect code is detected. It means you can check to make sure it doesn't cause problems and then if like in current C/C++ you can add a compiler directive to ignore the warning/error it is marked and the next time any work is carried out on that code it can be refactored.
For lecturers, there's nothing more tempting than teaching a language in which their students simply cannot make whole classes of mistake.
Bad! Very Bad! One of the best ways to learn is from your mistakes. If you never make a mistake you will never learn.
Imagine these wet behind the ears developers getting out into the real world, the language they are working on may not be what they where taught.
Years ago as a member of a motorcycle club we used to get our learner riders onto something like a CB250, GN250 SR250 etc. Nice single cylinder commuter style bikes with very good "nice" handling such that is they did stuff up they didn't drop the bike. By the time time they were ready for something bigger they had made all their mistakes.
Learning to code is the same.
The Register 
Biting the hand that feeds IT
Copyright. All rights reserved © 1998–2025
