1,514 karma · joined July 16, 2013
2 years is taking the piss. Seriously. I feel people have been programmed into thinking this is acceptable.
That will pull binary packages from ports builds on another machine and install and configure them.
So much goodness!
We have 25 people with Lumia 820's that are fine. I just got a bad battery.
1. feels closer to "old fashioned non-Canonical'ed UNIX" which I was brought up on.
2. Way less politics due to license.
3. Less crazy forking and wheel reinventing (basically everything Ubuntu isn't).
4. It has orders of magnitude better documentation
5. pkgng is actually really nice
6. separation of core OS vs ports/packages so easy to stage updates compared to catch all Linux distros.
7. pf is miles better than iptables
8. ZFS.
9. I have a Sun Ultra 30 sitting in my cupboard which Linux doens't like.
10. Has valgrind that works properly unlike the other BSD's.
That's about it but it's enough.
My use cases are: personal use, professional use (devops), professional use (production).
When that runs out, I can take it out and stick the other one in out of my bag.
I may actually consider dumping Debian for FreeBSD 10.
I've never been totally happy with Linux after moving off "proper" UNIX machines. I had a FreeBSD 4.4 machine floating around for years which I was rather happy with but drifted off to Linux-land primarily due to convenience when it came to Flash and audio.
So many compelling reasons to switch back to FreeBSD now.
It was. Nokia service sent me a new one out for nothing after a 5 minute phone call.
> You know what's also a safety nightmare? Batteries. Which is why stopping third-parties from replacing certified batteries with random bought-off-eBay batteries is definitely a good idea.
The problem is more power isolation. If you get a short when you damage the device etc (compression/impact/waterlogging), your typical LiPoly cell is going to catch fire or at least knock out extremes of heat. This is very hazardous. Removal batteries at least have a chance of power isolation.
My specific example here is my 2010 MBP which the battery was not glued (but inaccessible). This got waterlogged after a drink was spilled on the table. Turning it upside down revealed that capillary action around the base plate had sucked up the water. It rained on the logic board. About 30 seconds later, it caught fire. My only resort was to throw it in the garden and watch my £1249 investment burn up.
> Apple does have a recycling programme where you can bring your old electronics for free
Yes they do but perhaps if you could replace the battery out of warranty, you wouldn't need to recycle it :)
Nice work by the way. It's quite amazing the odd things you can do in Excel.
They're not a useful innovation - they are an abhorrent consumerist "disposalism" decision to pump sales, a safety nightmare (isolate it? nope), purely a cost cutting exercise for the manufacturer and make it even harder to recycle the nasty chemicals.
Don't give me the shit about it allowing smaller devices to be made either. You can make smaller devices with removable batteries fine.
I'm a qualified EE for ref.
When using the mouse, the transition is implied so it's annoying.
Great work though!
It doesn't make unicorns shit rainbows or defy the laws of physics.
If you did a submission somewhere, it'd do offline processing and upload new static pages.
Most of this was C and perl.
No Scala, no Java, no Ruby.
iOS does HTML too you know.
I agree with the OP - most of this new technology doesn't really solve any problems. All it does is create an ecosystem you can feel superior being a member of.
I've just replaced the battery on my Lumia 820 after 9 months. They don't last forever. Glue is inexcusable. If they had a half decent mechanical design, foam pads would secure it in place when the device was assembled and allow replacement.
I'd probably buy new Apple products if they weren't held together with glue. I'm not investing lots of money in something intended to be disposable. My last MBP (2010) was at least servicable. Now replaced with Lenovo kit as it's possible to strip it down and replace anything.
I will now go and hit myself with a LART for a bit to remember not to do that again.
peer reviewed demonstration or piss off.
You can actually do most of that with vanilla PowerShell and Excel believe it or not but it's much fuglier and you spend most of your way working around edge cases.
The only thing that scares me about this though is that JSON is a terrible format for storing numbers in. There is no way of specifying a decimal type for example so aggregations and calculations have no implied precision past floating point values.
That in itself is sign that a mistake can be made without noticing.
$ cat test2.c
int main(int argc, char *argv[]) {
if (argc = 0)
return 1;
return 0;
}
$ make test
cc -Wall -ansi -pedantic test.c -o test
$ cat test.c
int main(int argc, char *argv[]) {
if (0 == argc)
return 1;
return 0;
}
$ CFLAGS="-Wall -ansi -pedantic" make test
cc -Wall -ansi -pedantic test.c -o test
(0 == current->uid)
(current->uid == 0) // or (current->uid = 0) in this case.
"You are absolutely deluded, if not stupid, if you think that a worldwide collection of software engineers who can't write operating systems or applications without security holes, can then turn around and suddenly write virtualization layers without security holes."
Quotas are easy enough to enforce. Most UNIX derivatives (including Linux) have disk and process quotas, some for over 3 decades.
Virtualization seems to be best used for reselling (and overselling) hosts that are smaller than the physical machine and not much else. Migration/failover is a non issue if you know what you are doing and if you need larger machines, it's just more overhead on top of a dedicated host. Plus it's increased administrative cost and more expense as a whole.
Thanks for being rational - you are spot on.