The "mistake" was not his... since it's not particularly a mistake to feel like you want to know a person before asking them out on a date. Some people are okay with taking somebody who is still practically a stranger on a date, not everybody is, and not everybody can feel like they know somebody that well after just a couple of online chat or emails.
In fact, I'd argue the mistake is theirs, for not being communicative enough about their intentions. If they want somebody who moves faster, they should say so. Or at the very least, honestly let the guy go by telling him that they aren't feeling any sort of chemistry of connection with them, and admit that they think further communication would probably just be a waste of time at that point, as soon as they realize that they aren't interested in them, instead of just ignoring their messages.
More specifically, winehq does not particularly consider the distro worthy of supporting. That's a failing of winehq by my reckoning, not Slackware, specifically.
you may want to build Wine from source in a 32-bit chroot.
Running windows applications with various degrees of success (I've heard that.NET applications have a lot of trouble) is not sufficient incentive for me to create a 32-bit chroot that would offer me no other advantages, since I can already run 32-bit linux applications just fine.
It's not like Wine is an emulator or anything
It takes an existing binary compiled for a particular operating system/platform and runs it on a different one from that for which the binary was targeted. That makes it either a virtual machine or an emulator. Calling wine a virtual machine seems a bit of a stretch though. Is the only reason to not call it an emulator because its moniker says so?
If the monthly fee for a cell phone costs any more with a phone you've bought outright vs one you are getting as part of a contract plan, don't bother locking yourself in with them at all.
Bathroom breaks don't take half an hour. And meal breaks are taken when the location and time of day is agreeable, which *MIGHT* be, but is not particularly statistically likely to be at the exact same point or time that you always need to recharge.
While 30 minutes is great compared to waiting several hours, they need to really bring that recharge time down by a factor of 5 or more. Being able to stop for a recharge in many places is good, but for longer trips (which mentioning coast-to-coast travel seems to be pointing towards) waiting for half an hour every charging cycle will start to add up on your travel time.
If all manufacturers were required, by law, to follow the same standards, then the exact same facilities are equally available to everybody.
Where in the constitution does it say that the right to bear arms should be equivalent to the right for the bearer to decide on the fundamental design or engineering of those arms?
I have to wonder... is a person who opposes this kind of technology being mandatory in citizen weaponry of the opinion that those children deaths are an acceptable price to pay for their continued freedom to bear arms of their own chosen design?
Slashdot Mirror
For what it's worth, Unity3d doesn't work under WINE anyways.
The "mistake" was not his... since it's not particularly a mistake to feel like you want to know a person before asking them out on a date. Some people are okay with taking somebody who is still practically a stranger on a date, not everybody is, and not everybody can feel like they know somebody that well after just a couple of online chat or emails.
In fact, I'd argue the mistake is theirs, for not being communicative enough about their intentions. If they want somebody who moves faster, they should say so. Or at the very least, honestly let the guy go by telling him that they aren't feeling any sort of chemistry of connection with them, and admit that they think further communication would probably just be a waste of time at that point, as soon as they realize that they aren't interested in them, instead of just ignoring their messages.
Or, you know, maybe some people are just more comfortable actually getting to know the person first.
Of course they can. And that's what some of this new regulation will ensure.
So, no. Okay... Thanks.
More specifically, winehq does not particularly consider the distro worthy of supporting. That's a failing of winehq by my reckoning, not Slackware, specifically.
Running windows applications with various degrees of success (I've heard that .NET applications have a lot of trouble) is not sufficient incentive for me to create a 32-bit chroot that would offer me no other advantages, since I can already run 32-bit linux applications just fine.
It takes an existing binary compiled for a particular operating system/platform and runs it on a different one from that for which the binary was targeted. That makes it either a virtual machine or an emulator. Calling wine a virtual machine seems a bit of a stretch though. Is the only reason to not call it an emulator because its moniker says so?
Do you have any evidence for what you've said here, especially what's bolded above, that's not going to end up sounding like a conspiracy theory?
If the monthly fee for a cell phone costs any more with a phone you've bought outright vs one you are getting as part of a contract plan, don't bother locking yourself in with them at all.
"Contracts are now capped at two years"...
(sigh)
My contract is 2 years old next month.
I still have a year to go, and boy do I have grievances.
Running something under wine does not qualify as runnable under Linux.
Plus, I the distro I use doesn't support wine on a 64-bit platform yet.
Unity3d can build a target application that runs on Linux, but the development environment only runs on Windows or Mac
To be fair, they need to offer some sort of incentive to purchase it.
Although I agree with you... it's annoying. Just saying I understand it.
Can you provide any proof of that statement?
Developers *ARE* the end users of an API.
Already decided in court? Yes. Settled? Far from it.
This is about Oracle trying to appeal the former decision.
By that reasoning, then, wouldn't not being allowed to own automatic weapons or nuclear weapons be an equal infringement of the 2nd amendment?
Bathroom breaks don't take half an hour. And meal breaks are taken when the location and time of day is agreeable, which *MIGHT* be, but is not particularly statistically likely to be at the exact same point or time that you always need to recharge.
Where does it say this? Or is that just a plausible interpretation?
While 30 minutes is great compared to waiting several hours, they need to really bring that recharge time down by a factor of 5 or more. Being able to stop for a recharge in many places is good, but for longer trips (which mentioning coast-to-coast travel seems to be pointing towards) waiting for half an hour every charging cycle will start to add up on your travel time.
So... yes, then?
Got it. Thanks. Good to know.
If all manufacturers were required, by law, to follow the same standards, then the exact same facilities are equally available to everybody.
Where in the constitution does it say that the right to bear arms should be equivalent to the right for the bearer to decide on the fundamental design or engineering of those arms?
I have to wonder... is a person who opposes this kind of technology being mandatory in citizen weaponry of the opinion that those children deaths are an acceptable price to pay for their continued freedom to bear arms of their own chosen design?
On what basis? They wouldn't be saying that citizens can't have guns, only that they can only have guns which have been approved for citizen use.
... but before long, I expect that guns which are not classified as "smart" will be illegal for private citizens to manufacture or possess.