Spare a thought for the hardware engineers who have to suffer with languages that are derived from real languages with whatever the hardware engineers thought would be a good thing to add to make it a HDL. ADA -> VHDL, C-> Verilog, Verilog -> System Verilog, C -> System C.
I might design hardware but I have a CS degree and the horror of these carbuncles is not lost on me.
The macros in Verilog and System Verilog might just be the worst thing in any language anywhere. The absence of a fundamental logic bit type in VHDL means you need libraries before you can do anything. OVM is beyond the wit of man to comprehend from any modern language theory.
Re:Obligatory reminder that an alternative exists
on
OpenSSL 1.0.2 Released
·
· Score: 1
Yes, when I get back in the office and get the details. In hand wavey terms, 0 entropy in specfic VMs on specific headless servers, because it trusts the kernel to get it right.
but you still have to use ctrl c and ctrl x. how does it help to have a dedicated ctrl v button? seems like a strange hill to die on to insist on a 3 button mouse. don't you think?
The last time I checked, ctrl-c interrupts the running process.
"Mice", please! "Mouses" [shudder] is just painful to read.
You are wrong. The creator of computer mouses himself, Douglas Engelbart, stated that the plural of a computer mouse is mouses. The plural of the small mammal of the same name is mice.
A real computer is a computer on which the left button drag-select also copies the selected text, so you can immediately paste it by middle clicking somewhere.
Such a machine is usually running X windows.
Re:Obligatory reminder that an alternative exists
on
OpenSSL 1.0.2 Released
·
· Score: 1
And they got swallowed up by ARM, so don't count on cross platform compatibility.
With any security software, just because it runs, it doesn't mean it works.
Re:Obligatory reminder that an alternative exists
on
OpenSSL 1.0.2 Released
·
· Score: 5, Informative
We tried contacting the PolarSSL developers about contributing code to fix their random number problem. No response. No random numbers -> no security.
No matter what the security problem, it's always the random numbers, or lack thereof that is the problem.
Or maybe people who really know what they're doing aren't going to be that confident that they're safe.
Indeed. That's where I am concerning phones and PCs. I'm good with the hardware because I design it. But in my job I'm exposed to all the darkest security concerns, so there's lots to be concerned about.
The corps have been stupid to present this as a skills shortage issue. They are in competition for skilled staff and so the shortage they feel is just a property of the system, not a property of how many skilled people there are.
What it is is about gaining access to skilled staff from abroad. By making it easy for people with the right skills to come to the US, they provide those companies with easier access to the world's population of skilled staff, rather than just the US population.
This should be presented as competing internationally by hanging onto all the best people.
>those who are confident of their computer knowledge were at greater risk for data leaks.
Doesn't that depend on why they are confident? If you're confident because you don't know what you don't know then maybe it's valid but if you're confident because you happen to have been designing computers for 30 years and are deeply involved in security architecture of computers, then maybe your confidence is well placed.
I had to refile for 2 years ago after the IRS 'found' a 1099 I was unaware of, because it was from a broker I quit using, so it was not available to me on the broker we site.
The IRS had it. The broker had it. I didn't have it.
I can program and I maintain the web site of our family business with as much static html as possible. The actual places where dynamism is required (E.G. class bookings) is handled with CGI in python. Credit card processing is farmed out to stripe.
Thus the total amount of code that needs to be comprehended is small. A few hundred lines.
The long term savings in terms of enabling staff to go in and edit stuff live has saved a fortune.
What works for one business may not work for another. I tried Django and the sheer volume of stuff I needed to do to get the same functionality up was huge and then the staff couldn't edit it because for all that's claimed for Django, there's a big model you have to get in you head before you can start meddling with it, and that means web professionals who cost a lot of money.
The incumbent film studios don't release many films for home streaming because they think people will have to go to the theater or buy the DVD.
The filmmakers would generally prefer theatrical, since it has the best reach, tends to present the work in the highest quality, and contractual royalties and residuals are most favorable to theatrical release.
The studios (the "producers" and production companies) are indifferent, they like making money off the movie wherever. They prefer theatrical because theatrical usually produces the most revenue but this isn't always true for all films.
The distribution companies would love to launch everything day-in-date, and they love streaming since they usually get a fatter cut of the revenue.
The theaters (the "theatrical exhibitors") are hell bent against day-in-date streaming because they believe they'll lose attendance to it. When a studio attempts to release a movie day-in-date on streaming or DVD, like Universal tried to do with Tower Heist, the theaters band together and refuse to release the movie. Theater chains generally won't agree to screen a film without a contractual blackout period.
There's no reason why Samba would benefit from being dependent on systemd. OpenRC provides the same functionality as systemd's init process, and smbd and nmbd are already long-running daemons, additional instances of which are managed by the initial daemon. Tools like daemontools (or, you know, init) already exist to start (and if necessary, restart) long-running daemons.
SaMBa is used in far too many places to really want to take on systemd as a dependency. It's used on everything from traditional Unix systems (HP-UX, AIX, Solaris) to Apple's MacOS, Linux, and embedded devices running Linux or a BSD. It would make zero sense for them to require systemd as a result.
This is also one of the issues that many, including myself, take with systemd since it now makes it harder to write portable software - one of the reasons many devs went to Linux from Windows.
samba.c: if (systemd_present) do_systemd_stuff() else do_other_stuff()
Have run this through my head, having been in big corporations for long enough to know how this works, I'll hypothesize that:
1) Someone scheduled these interviewers to do an interview at a specific time. They had no interaction with each other wrt the interview. 2) The individual interviewers had no clue she was there for 5 hours. 3) Someone, probably an admin in HR, booked the room, scheduled the interviewers and didn't think to schedule a break time or a pre-post meeting for the interviewers. 4) That someone was probably a woman.
The issue is the source of entropy, not the post processing.
Ditto. I was happy as a pig in shit programming Pascal in 1987. Compared to Apple Basic it had types.
>Assembler (who codes in that any more, though?).
Er me. But I work for a company that builds CPUs. So it's usually to bang on corner cases.
Spare a thought for the hardware engineers who have to suffer with languages that are derived from real languages with whatever the hardware engineers thought would be a good thing to add to make it a HDL. ADA -> VHDL, C-> Verilog, Verilog -> System Verilog, C -> System C.
I might design hardware but I have a CS degree and the horror of these carbuncles is not lost on me.
The macros in Verilog and System Verilog might just be the worst thing in any language anywhere.
The absence of a fundamental logic bit type in VHDL means you need libraries before you can do anything.
OVM is beyond the wit of man to comprehend from any modern language theory.
Reeces meeces pieces?
Yes, when I get back in the office and get the details. In hand wavey terms, 0 entropy in specfic VMs on specific headless servers, because it trusts the kernel to get it right.
I learned that during a lecture in college circa 1989. But this is the best I could find.. http://alt-usage-english.org/e...
http://www8.hp.com/us/en/produ...
That was easy.
but you still have to use ctrl c and ctrl x. how does it help to have a dedicated ctrl v button? seems like a strange hill to die on to insist on a 3 button mouse. don't you think?
The last time I checked, ctrl-c interrupts the running process.
on a lot of the mouses ...
"Mice", please! "Mouses" [shudder] is just painful to read.
You are wrong. The creator of computer mouses himself, Douglas Engelbart, stated that the plural of a computer mouse is mouses.
The plural of the small mammal of the same name is mice.
A real computer is a computer on which the left button drag-select also copies the selected text, so you can immediately paste it by middle clicking somewhere.
Such a machine is usually running X windows.
And they got swallowed up by ARM, so don't count on cross platform compatibility.
With any security software, just because it runs, it doesn't mean it works.
We tried contacting the PolarSSL developers about contributing code to fix their random number problem. No response. No random numbers -> no security.
No matter what the security problem, it's always the random numbers, or lack thereof that is the problem.
>Croft says that the battery pulls 1 nanoAmp each time it oscillates between the bell’s sides, which is an exceedingly low amount of energy
That isn't a unit of energy. It tells you nothing about the energy consumed.
Or maybe people who really know what they're doing aren't going to be that confident that they're safe.
Indeed. That's where I am concerning phones and PCs. I'm good with the hardware because I design it. But in my job I'm exposed to all the darkest security concerns, so there's lots to be concerned about.
The corps have been stupid to present this as a skills shortage issue. They are in competition for skilled staff and so the shortage they feel is just a property of the system, not a property of how many skilled people there are.
What it is is about gaining access to skilled staff from abroad. By making it easy for people with the right skills to come to the US, they provide those companies with easier access to the world's population of skilled staff, rather than just the US population.
This should be presented as competing internationally by hanging onto all the best people.
In my experience, non techy users (we run a yarn store) do know HTML. They don't know a markdown language.
>those who are confident of their computer knowledge were at greater risk for data leaks.
Doesn't that depend on why they are confident? If you're confident because you don't know what you don't know then maybe it's valid but if you're confident because you happen to have been designing computers for 30 years and are deeply involved in security architecture of computers, then maybe your confidence is well placed.
This.
I had to refile for 2 years ago after the IRS 'found' a 1099 I was unaware of, because it was from a broker I quit using, so it was not available to me on the broker we site.
The IRS had it. The broker had it. I didn't have it.
I can program and I maintain the web site of our family business with as much static html as possible. The actual places where dynamism is required (E.G. class bookings) is handled with CGI in python. Credit card processing is farmed out to stripe.
Thus the total amount of code that needs to be comprehended is small. A few hundred lines.
The long term savings in terms of enabling staff to go in and edit stuff live has saved a fortune.
What works for one business may not work for another. I tried Django and the sheer volume of stuff I needed to do to get the same functionality up was huge and then the staff couldn't edit it because for all that's claimed for Django, there's a big model you have to get in you head before you can start meddling with it, and that means web professionals who cost a lot of money.
The filmmakers would generally prefer theatrical, since it has the best reach, tends to present the work in the highest quality, and contractual royalties and residuals are most favorable to theatrical release.
The studios (the "producers" and production companies) are indifferent, they like making money off the movie wherever. They prefer theatrical because theatrical usually produces the most revenue but this isn't always true for all films.
The distribution companies would love to launch everything day-in-date, and they love streaming since they usually get a fatter cut of the revenue.
The theaters (the "theatrical exhibitors") are hell bent against day-in-date streaming because they believe they'll lose attendance to it. When a studio attempts to release a movie day-in-date on streaming or DVD, like Universal tried to do with Tower Heist, the theaters band together and refuse to release the movie. Theater chains generally won't agree to screen a film without a contractual blackout period.
The Customers presumably don't count.
Since when was the security community close knit?
* Samba, yes, because it's a daemon.
There's no reason why Samba would benefit from being dependent on systemd. OpenRC provides the same functionality as systemd's init process, and smbd and nmbd are already long-running daemons, additional instances of which are managed by the initial daemon. Tools like daemontools (or, you know, init) already exist to start (and if necessary, restart) long-running daemons.
SaMBa is used in far too many places to really want to take on systemd as a dependency. It's used on everything from traditional Unix systems (HP-UX, AIX, Solaris) to Apple's MacOS, Linux, and embedded devices running Linux or a BSD. It would make zero sense for them to require systemd as a result.
This is also one of the issues that many, including myself, take with systemd since it now makes it harder to write portable software - one of the reasons many devs went to Linux from Windows.
samba.c:
if (systemd_present) do_systemd_stuff()
else
do_other_stuff()
In my experience, the people who don't get jobs interview a lot more. People who get jobs easily, don't do as many interviews.
It only takes a few women working full time to provide 20% of the interview candidates for most of the interviews in silicon valley.
The tech companies should interview women for the position of full time bad interviewees and pay them to do it. Instant quota filling.
Meanwhile, men and women who like tech and are good at it can get on with making chips and software and little boxes with leds on them.
Have run this through my head, having been in big corporations for long enough to know how this works, I'll hypothesize that:
1) Someone scheduled these interviewers to do an interview at a specific time. They had no interaction with each other wrt the interview.
2) The individual interviewers had no clue she was there for 5 hours.
3) Someone, probably an admin in HR, booked the room, scheduled the interviewers and didn't think to schedule a break time or a pre-post meeting for the interviewers.
4) That someone was probably a woman.
Yes, guys spend five hours interviewing for a tech position without seeing any men, that happens all the time.
So they've got to have the women on staff before they are allowed to interview women to get them on the staff?!