While BSD it will just fail to recognize the device.
It may not recognize the device as "something" but it will always recognize the device. Any time I have a problem with a USB device on Windows I'll plug it into a FreeBSD machine and it'll tell me exactly what it is, no obfuscation
However for Personal Computing they suck,
My wife's laptop aside, in which she's happy with Windows 8 everything in my house is FreeBSD of some sort. Down to my HTPC which is FreeBSD running Kodi. All of the sound devices, including SPDIF out, are recognized. It was easier to setup than Kodi on Windows.
if you could point out "crap" hardware, explain why it's crap,
If the vendor doesn't think it is worth their time to develop drivers for it then it must not be good enough to develop drivers for.
I already gave the RealTek vs Intel Ethernet drivers.
Another is Nvidia vs AMD/ATI. I hand Nvidia money. Nvidia hands me a working video driver. No reverse engineering needed. No "here's a bunch of specs, write your own driver".
Yet another is Supermicro and Intel motherboards vs consumer boards. Turns out Intel and Supermicro designs and develops motherboards with full driver support. Most consumer boards I've seen will toss in Realtek drivers and a bunch of other cheap chips to save a penny or so with the end result being no driver support in Linux or FreeBSD. Windows drivers are still hit or miss.
Hardware was poorly supported with frequent system crashes.
This is the trick I've figured out with FreeBSD: They don't support crap hardware. The best hardware support comes from companies that pay developers to make FreeBSD drivers. (See RealTek vs Intel ethernet drivers). If you look at who the core users of FreeBSD are and look at who sponsors development it's mostly servers.
For most of my desktops I've returned to server hardware anyway. Whitebox builds were fun when I was poor and my time was free. But after the N'th time of dicking around with figuring out why my Motherboard and RAM won't play nice or the monster heat sink I added scrubbed off traces I'd rather just buy a machine that's supported.
Buy good hardware. Get good results.
so bugs are infrequently reported and the lack of developers means that bugs often go unfixed.
I've had the opposite experience. Bugs are so infrequent that if it's not a PEBKAC error then the FreeBSD guys can usually drill down to the bottom of it quick. If it's a problem someone else has experienced then the fix is most likely out there already anyway. Google will return results with the error I'm having instead of threads of noise from the Ubuntu forums.
often failed to properly build software
[Pics or it didn't happen].
Even if you somehow screwed the system up so bad that ports wouldn't build, there's always pkg.
I once had a port try to build and install a rootkit in the process.
It has everything 'pretty' that Ubuntu could have, minus the weirdness of a kFreeBSD/GNU userland. It sets everything up from install. You can even select what window manager you want to use during install.
Personally bare FreeBSD itself is just fine if the command line doesn't scare you. It takes less time to install FreeBSD and the 5-10 packages needed to get to a 'normal' desktop than it does to install any version Windows. I'm just kicking myself for not making the switch earlier.
Additionally. Describing projects as "For Humans" must stop. FreeBSD is already for humans. I could teach a middle schooler to install it and get to Facebook. It's honestly not that hard.
don't have a problem that a whole lot of other people complain about, obviously the problem simply doesn't exist.
Having spent more than enough time playing anthropologist on TRP and other similar sites and pages it boils down to "a whole lot of other people" are massive assholes.
...one loaded with blind assumptions (more like accusations) about the people who do have this problem.
When you read half of the stuff that comes out of their mouth it's not very blind.
A sad bunch of man children that toss about words like "alpha" and "beta males" while whining they can't get laid. All while talking down to women, treating them like the 'smartest teenagers in the room'. It doesn't take a lot of time reading what they post to see where the problems are.
You do know that telling people about this place is going to drive more traffic to it.
At this point the signals completely lost in the noise anyway.
It's one of the few places anywhere where men don't get shamed for wanting to have sex.
Odd. I've never had that problem. Nor any of the other problems that TRPers whine about. Then again I don't act like women are vending machines dispensing sex after enough nice guy tokens are entered or any of the other random problems they have. Hell my female friends never shamed me for wanting sex. (But That means I also had female friends, a concept beyond most TRPers).
Nobody ITT has done anything to communicate safety in terms the general populace will accept.
And they've been conveyed in terms they will understand how the RTOS on their current car runs? Or how open heart surgery works? Or how any number of things they use daily work? Or do they leave it up to people that do that for a living.
'wait, lets analyze this'.
We ARE analyzing it. We have been for decades. You refuse to listen to engineers that have actually done stuff similar. You've come up with the easiest and lowest hanging fruit as 'problems' and then refuse to listen to any solution anyone comes up with. It's fairly evident that no one else coming up with these 'crazy impossible problems' is an engineer. I haven't seen anything ITT that is non-trivial.
I even posted the tools we use to simulate real world scenarios and you refused to accept that it could possibly be correct. As if companies are spending millions+ on these devices because they don't simulate things accurately.
After almost two decades on Slashdot and a decade in industry it's dead accurate. You guys whine constantly about new technology. I can almost guarantee most of you are the guys in the office that insist on doing things 'the way you learned them' 20 or 30 years ago. Where I work you're the barriers to progress. Up to a point it's just cheaper to keep you around until it's easier to start over with a fresh grad or a H1B and train them on new tools.
This isn't a CS problem, this is a mechanical engineering / dynamics problem. Sometime along the way they figured out it would be easier to teach engineers to code than it was to teach coders to engineer. We use tools that most of Slashdot thinks don't even exist, like Simulink (a drag and drop coding language of sorts).
but lets do some *real* due diligence before we so blindly strap ourselves in.
We are. But the test cases that you've come up with are quite literally the lowest hanging fruit there is. A flat tire? Most cars auto driving is going to come with first come with run flats. (BMW, Benz). For those that don't it's still one of the simplest FMEAs to possibly do. You put a car in the test cell and blow the tires over and over and over, collect data, toss it in the HIL and test your controller. Toss the controller on a car. Repeat.
And I can guarantee that the self driving car is going to handle a blown tire better than you ever will. It'll handle it better than race car drivers will.
and you don't grow old by being stupid.
And you don't stay gainfully employed by doing things the old way.
You think that we use them because they don't correlate to real world testing? We just have an extra $100k laying around and go "Hey, lets buy one of those expensive dSpace things. It doesn't correlate at all to real world data but it'd be a cool space heater."
These 'But will it work when towing my red unicorn trailer up a mountain pass that gets 90 cm of snow annually!?!?!" cases are hilarious.
Why do you even care where the car is parked? Personal car ownership is going to go the way of personal horse ownership. You order a car it takes you from A to B and goes to the next customer.
Are you kidding me? Your argument boils down to "I don't know how to program this, therefore it can't be done".
"We" do this all the time. Often on dSpace HIL benches to simulate the dynamics of a failure and in the real world. What happens if we lose this sensor, what happens if we lose that sensor, what happens if this sensor.
A tire blow out is an absolutely trivial problem to program around.
Think about the visual problems that would occur from the shaking and vibrations of that event?
Google for 'low pass filter'. Hell you could probably run to stop open loop based on last good data.
Reading these stories you can tell that most Slashdotters aren't controls engineers. Stick to coding websites and what ever else you do.
See. The immediate jump to "If you're not with us, you're against us" appeal.
No I'm not a MRA, anti-feminist and hated Frats. But for someone in the middle "SJWers" are no different than them just in the opposite direction. Most of the time I'll just get popcorn and sit on the sidelines and watch those two sides go at it but when one side disproportionately starts taking over my media then it gets annoying.
So unless you're willing to accept a counterbalance of pro-MRA/anti-feminist/frat house stories then there is nothing to counterbalance the "SJW". And no, the lack of these types of stories does not mean that there is pro-counter arguments.
So by banning these stories you bring Slashdot back to center. Allowing these stories tilts it left. So to return to center either you get rid of these stories or you start posting pro-MRA articles. But the lack of your side does not immediately make the site "the other side".
That's exactly who it is. These are the people that will tell a woman that her opinion is wrong because of "internalized misogyny". The only correct position is *theirs*. Most are white women that came from families with money. On their scale of positions in life they still rank themselves below a poor white male from Appalachia.
And they also have a Patreon setup so they can continually do nothing, be outraged at others that do stuff and get paid.
And after you stop running the blackface show and start pandering to the blacks. But no matter what you say or do they'll find something else to whine about. Say you put a bunch of them in a new movie, they'll complain that it's somehow sexist. No matter what you do to appease this crowd they just constantly whine. And the new crowd, when they come in, tells you they don't even drink beer. They aren't really drinkers. But they sit and whine about how other people drink beer constantly.
Not only that your old customers have moved on to a new bar. Your new patreons don't actually bring more money in to the bar (since they don't seem to have actual jobs). They don't attract any new customers like them anyway since they don't seem to ever be content with what you do to pander to them, they just like complaining for the sake of complaining.
Slashdot Mirror
Let me guess. "Le last guys finish last"
PC-BSD
While BSD it will just fail to recognize the device.
It may not recognize the device as "something" but it will always recognize the device. Any time I have a problem with a USB device on Windows I'll plug it into a FreeBSD machine and it'll tell me exactly what it is, no obfuscation
However for Personal Computing they suck,
My wife's laptop aside, in which she's happy with Windows 8 everything in my house is FreeBSD of some sort. Down to my HTPC which is FreeBSD running Kodi. All of the sound devices, including SPDIF out, are recognized. It was easier to setup than Kodi on Windows.
if you could point out "crap" hardware, explain why it's crap,
If the vendor doesn't think it is worth their time to develop drivers for it then it must not be good enough to develop drivers for.
I already gave the RealTek vs Intel Ethernet drivers.
Another is Nvidia vs AMD/ATI. I hand Nvidia money. Nvidia hands me a working video driver. No reverse engineering needed. No "here's a bunch of specs, write your own driver".
Yet another is Supermicro and Intel motherboards vs consumer boards. Turns out Intel and Supermicro designs and develops motherboards with full driver support. Most consumer boards I've seen will toss in Realtek drivers and a bunch of other cheap chips to save a penny or so with the end result being no driver support in Linux or FreeBSD. Windows drivers are still hit or miss.
I just tested it. Sleep works fine as well. The documentation on it is straight forward and easy to read: https://www.freebsd.org/doc/ha...
Tested it and it works fine.
Dell M6800.
wifi
Yes. It's even detected during FreeBSD's install and I can finish the installation on Wifi.
sound
Yes. And it's hands down better than the spaghetti mess that is sound on Linux.
LCD Panel
Yes. Nvidia even takes some of the money I give them and pays someone to develop drivers for the graphics card.
sleep mode work after the install,
I don't know, but I never used sleep on Windows or Linux so it's not a use case that I've tested.
Hardware was poorly supported with frequent system crashes.
This is the trick I've figured out with FreeBSD: They don't support crap hardware. The best hardware support comes from companies that pay developers to make FreeBSD drivers. (See RealTek vs Intel ethernet drivers). If you look at who the core users of FreeBSD are and look at who sponsors development it's mostly servers.
For most of my desktops I've returned to server hardware anyway. Whitebox builds were fun when I was poor and my time was free. But after the N'th time of dicking around with figuring out why my Motherboard and RAM won't play nice or the monster heat sink I added scrubbed off traces I'd rather just buy a machine that's supported.
Buy good hardware. Get good results.
so bugs are infrequently reported and the lack of developers means that bugs often go unfixed.
I've had the opposite experience. Bugs are so infrequent that if it's not a PEBKAC error then the FreeBSD guys can usually drill down to the bottom of it quick. If it's a problem someone else has experienced then the fix is most likely out there already anyway. Google will return results with the error I'm having instead of threads of noise from the Ubuntu forums.
often failed to properly build software
[Pics or it didn't happen].
Even if you somehow screwed the system up so bad that ports wouldn't build, there's always pkg.
I once had a port try to build and install a rootkit in the process.
[Citation Needed]
It has everything 'pretty' that Ubuntu could have, minus the weirdness of a kFreeBSD/GNU userland. It sets everything up from install. You can even select what window manager you want to use during install.
Personally bare FreeBSD itself is just fine if the command line doesn't scare you. It takes less time to install FreeBSD and the 5-10 packages needed to get to a 'normal' desktop than it does to install any version Windows. I'm just kicking myself for not making the switch earlier.
Additionally. Describing projects as "For Humans" must stop. FreeBSD is already for humans. I could teach a middle schooler to install it and get to Facebook. It's honestly not that hard.
and there are a bunch of single engineers right here, and they can't land dates...what might the reason be?
No one ever told them they were assholes?
don't have a problem that a whole lot of other people complain about, obviously the problem simply doesn't exist.
Having spent more than enough time playing anthropologist on TRP and other similar sites and pages it boils down to "a whole lot of other people" are massive assholes.
...one loaded with blind assumptions (more like accusations) about the people who do have this problem.
When you read half of the stuff that comes out of their mouth it's not very blind.
If the girl has great tits and ass, I can't be friends with her.Simple as that
Who cares about a woman's personality if she's not hot enough to make my dick get hard?
A sad bunch of man children that toss about words like "alpha" and "beta males" while whining they can't get laid. All while talking down to women, treating them like the 'smartest teenagers in the room'. It doesn't take a lot of time reading what they post to see where the problems are.
You do know that telling people about this place is going to drive more traffic to it.
At this point the signals completely lost in the noise anyway.
It's one of the few places anywhere where men don't get shamed for wanting to have sex.
Odd. I've never had that problem. Nor any of the other problems that TRPers whine about. Then again I don't act like women are vending machines dispensing sex after enough nice guy tokens are entered or any of the other random problems they have. Hell my female friends never shamed me for wanting sex. (But That means I also had female friends, a concept beyond most TRPers).
I keep hearing this. It's an anecdote that doesn't hold true in my circles.
Sssh. You'll upset RedPill theory. Let them convince themselves that there aren't any women out there and they don't want engineers.
Nobody ITT has done anything to communicate safety in terms the general populace will accept.
And they've been conveyed in terms they will understand how the RTOS on their current car runs? Or how open heart surgery works? Or how any number of things they use daily work? Or do they leave it up to people that do that for a living.
'wait, lets analyze this'.
We ARE analyzing it. We have been for decades. You refuse to listen to engineers that have actually done stuff similar. You've come up with the easiest and lowest hanging fruit as 'problems' and then refuse to listen to any solution anyone comes up with. It's fairly evident that no one else coming up with these 'crazy impossible problems' is an engineer. I haven't seen anything ITT that is non-trivial.
I even posted the tools we use to simulate real world scenarios and you refused to accept that it could possibly be correct. As if companies are spending millions+ on these devices because they don't simulate things accurately.
After almost two decades on Slashdot and a decade in industry it's dead accurate. You guys whine constantly about new technology. I can almost guarantee most of you are the guys in the office that insist on doing things 'the way you learned them' 20 or 30 years ago. Where I work you're the barriers to progress. Up to a point it's just cheaper to keep you around until it's easier to start over with a fresh grad or a H1B and train them on new tools.
This isn't a CS problem, this is a mechanical engineering / dynamics problem. Sometime along the way they figured out it would be easier to teach engineers to code than it was to teach coders to engineer. We use tools that most of Slashdot thinks don't even exist, like Simulink (a drag and drop coding language of sorts).
but lets do some *real* due diligence before we so blindly strap ourselves in.
We are. But the test cases that you've come up with are quite literally the lowest hanging fruit there is. A flat tire? Most cars auto driving is going to come with first come with run flats. (BMW, Benz). For those that don't it's still one of the simplest FMEAs to possibly do. You put a car in the test cell and blow the tires over and over and over, collect data, toss it in the HIL and test your controller. Toss the controller on a car. Repeat.
And I can guarantee that the self driving car is going to handle a blown tire better than you ever will. It'll handle it better than race car drivers will.
and you don't grow old by being stupid.
And you don't stay gainfully employed by doing things the old way.
Why do I care about what someone's opinion on simulation is? I'll look at the data.
- Simulation is as good as the real thing.
This is how I can tell you're not an engineer. In engineering nothing is perfect. It's always 'good enough'.
If you're indicative of the average Slashdot user that's scared of technology it's no wonder you're being replaced by H1Bs.
You think that we use them because they don't correlate to real world testing? We just have an extra $100k laying around and go "Hey, lets buy one of those expensive dSpace things. It doesn't correlate at all to real world data but it'd be a cool space heater."
These 'But will it work when towing my red unicorn trailer up a mountain pass that gets 90 cm of snow annually!?!?!" cases are hilarious.
Why do you even care where the car is parked? Personal car ownership is going to go the way of personal horse ownership. You order a car it takes you from A to B and goes to the next customer.
But there's no way to simulate the real world failures like you're asserting has been done.
https://www.dspace.com/en/pub/...
We do it every single day.
Are you kidding me? Your argument boils down to "I don't know how to program this, therefore it can't be done".
"We" do this all the time. Often on dSpace HIL benches to simulate the dynamics of a failure and in the real world. What happens if we lose this sensor, what happens if we lose that sensor, what happens if this sensor.
A tire blow out is an absolutely trivial problem to program around.
Think about the visual problems that would occur from the shaking and vibrations of that event?
Google for 'low pass filter'. Hell you could probably run to stop open loop based on last good data.
Reading these stories you can tell that most Slashdotters aren't controls engineers. Stick to coding websites and what ever else you do.
Permanently offended, and those saying offensive things should be silenced because it creates negative consequences for some people.
(The permanently offended people in this case aren't the MRAs)
Then you'll get complaints that you don't have anyone that identifies as a cat.
MRA/anti-feminist/frat house toilet
See. The immediate jump to "If you're not with us, you're against us" appeal.
No I'm not a MRA, anti-feminist and hated Frats. But for someone in the middle "SJWers" are no different than them just in the opposite direction. Most of the time I'll just get popcorn and sit on the sidelines and watch those two sides go at it but when one side disproportionately starts taking over my media then it gets annoying.
So unless you're willing to accept a counterbalance of pro-MRA/anti-feminist/frat house stories then there is nothing to counterbalance the "SJW". And no, the lack of these types of stories does not mean that there is pro-counter arguments.
So by banning these stories you bring Slashdot back to center. Allowing these stories tilts it left. So to return to center either you get rid of these stories or you start posting pro-MRA articles. But the lack of your side does not immediately make the site "the other side".
That's exactly who it is. These are the people that will tell a woman that her opinion is wrong because of "internalized misogyny". The only correct position is *theirs*. Most are white women that came from families with money. On their scale of positions in life they still rank themselves below a poor white male from Appalachia.
And they also have a Patreon setup so they can continually do nothing, be outraged at others that do stuff and get paid.
And after you stop running the blackface show and start pandering to the blacks. But no matter what you say or do they'll find something else to whine about. Say you put a bunch of them in a new movie, they'll complain that it's somehow sexist. No matter what you do to appease this crowd they just constantly whine. And the new crowd, when they come in, tells you they don't even drink beer. They aren't really drinkers. But they sit and whine about how other people drink beer constantly.
Not only that your old customers have moved on to a new bar. Your new patreons don't actually bring more money in to the bar (since they don't seem to have actual jobs). They don't attract any new customers like them anyway since they don't seem to ever be content with what you do to pander to them, they just like complaining for the sake of complaining.