Honestly, it scares me that vanilla FTP is so widely used and the defacto way to transfers files for so many services. Its completely unencrypted.
Er, not everything needs to be encrypted. Having it as an option is great, but for non-sensitive data (e.g., source code that I'm already making available to the world) I'll take the protocol with the lower overhead.
remember how they said that we'll all be using Netbooks??
Yep. This post it being written from one, and it's really rather nice. That said, I'm running Xubuntu, as Windows 7 crawled when I had it on here. MS really does need to remember how to make a lean, fast, and usable OS. Right now they've got market share, but the only way to keep that is to stay ahead of the game. As they say, complacency kills.
Netbooks were killed by the simple fact that I can now get a full-size notebook for $350, so why would I want a DVD-less netbook for the same price?
Because it's half the size and the battery lasts longer. Though with Intel's crappy Atom chipsets perhaps the second part is no longer true.
Quite the contrary - I got one of the newish Atom netbooks (dual core), and its battery life is just perfect, provided I don't do anything really squirrelly, like sudo renice -19 -p $$ && sudo ionice -c 1 -p $$ && make -j12. At which point, I'd reasonably expect the battery life to drop on just about anything, given a complex enough code base.
I cheat. I write python code that writes its own plain C code, compiles it then executes it. this way, I work once to write a C template, that I then reuse through a high level language. and when I combine the advantages of python (sympy for instance) with the speed of C, I get stuff that is ridiculously faster than what I did before. in the sense that I don't work a lot to write it, and I don't wait around a lot for it to actually run afterwards. working with numerical simulations, I'm allowed to cheat this way...
Might be a silly question, but have you given Cython a shot? It sounds like you're doing something very similar to what their project was built to do.
So basically, you get around Python's performance limitations... by using C instead.
Way to go!
Why not? Use the right tool for the job. Though I'm curious if the parent has tried Cython. It seems like it might be a better fit for what they're doing.
Indeed, D2 looks amazing. And as I've said before, I love C++.
I'm curious as to how the C and C++ interop fronts are for D, though. I mean, one of the big reasons C++ hasn't gone away is the enormous amount of libraries written in it. Lua has Luabind, Python has Boost.Python
Serious question - I haven't had a chance to look into it myself.
How is that relevant? Nobody uses C++ for OS kernels.
That's not quite true. But close.
Indeed. Add onto all of those the fact that, AFAIK, on Linux, completely static linking a project is damn near impossible.
If you know otherwise, please let me know. I love the hell out of the language (yes, yes, I'm insane) but this kind of shit kills me. Is it so much to ask, to want to be able to compile a program and simply drop it onto another machine, without having to worry about what version of the standard libraries that machine has installed?
I can understand the issue with network libraries - C has issues with those, as well. But for basic applications - a non-networked game, for instance - this sort of limitation is annoying.
just hook into a repository for your distro and let it do the work for you.
This works, until you find that the version of $LIBRARY available in your distribution's repo is old as dirt - and the unofficial ones floating around online aren't much better - and you want to write software that has the latest features, bug fixes, etc. Then it's back to compiling and dependency tracking...
But, because there is a large influx of semi-skilled people who think that the fact they installed Ubuntu on their PC at home makes them a sever admin
While I won't say that it does make them a server admin, everyone has to start somewhere, and a lot of schools these days leave out a lot when it comes to technology. A friend of mine graduated with a Comp Sci degree a few years ago, and had barely touched anything *nix at all. I think they might have had them log into an old RHEL VM and use pico, perhaps start and stop apache, but that was it. This isn't to say that he wasn't smart, it's just that they didn't teach him anything outside of VB.NET and (how it use it to work with) XML.
I've since met and worked with others who had similar experience, if you s/VB.NET/Java/
Not precisely what I'd consider a broad range of education.
- require https over http to devices, yet still have telnet access enabled.
I'm sure I have several devices on my network with telnet enabled. Why should I bother disabling it? I don't use it, so its vulnerability to password sniffing is irrelevant.
I'm curious as to why you wouldn't disable telnet on those devices, if you don't use it.
I had a test OSX server at my last job I was at. Pretty much closed all ports except for 80 and whatever port Apple RDP ran on (actually, I closed that down at first, oops, had take a macbook into the server room to fix that), then opened up ports as needed.
I'm sure you realize this now, but for the sake of anyone else reading this you could have saved yourself a trip to the server room had you left 22 open; most OSX services can stopped and started via command line, just like any other *nix. I could be wrong (I don't use Mac's often), but I think they stick them in
As far as not using sudo, I think it depends on what you're doing. For example, if you're just running a single command, it makes sense to sudo (e.g., editing
Recent research has tended to show that the Abominable No-Man is being replaced by the Prohibitive Procrastinator. -- C.N. Parkinson
