Archived threads in /g/ - Technology - 7416. page

>>56175519
I mean shit if the guy wants the website to be "clean" then I don't see much wrong with that

But yeah, he's overreacting like a faggot

Say linux sucks or amd sucks and you will find triggered manchilds here who completly ignore every fact not suitable for their delusions like how you find triggered feminists on tumblr

Same shit different words

>>56175519
>then go ahead and vomit you weak faggot

port scanning isn't a crime
exploitation and unauthorized access is, though

>>56175506
>whole of cuba's ssh ports
that's only like 16 ports

Yes, your isp

>>56175374
Probably no recent sat imagery that is free, low res anyway. Depending on what you actually want you might want to look into drones instead.

There was one that charged on demand and guaranteed 2 hours ago pics. Can't remember the name though.

I don't know anything about camera operation so I'll ask:

How difficult would it be to have a camera set up that would just snap a picture every 30 minutes?

>>56175333
>Works only with vanilla 4chan
The quote green really hurts on light grey

ricer desktop and a thinkpad x220/230

>>56175157
a gaming laptop is not the most efficient way to spend your bills.
go for a well built desktop + potatobook

>>56175225
I wasn't quite thinking full gamer laptop but your conclusion still matches what I was seeing. A laptop with a gpu and nice screen got expensive fast.

>>56175124
DUDE

you have a DELL

File: serveimage.jpg (51KB, 500x344px) Image search: [Google]

51KB, 500x344px

Basically

>>56175115
>Systemd-Mount
Are you pretending that's a new thing or is it just your severe autism?

Poettering looks at a tool and thinks: "Wow, this is a 100 lines of code CLI around a system call? I should rewrite that in 10.000 lines of code with tons of XML parsing and DBUS integration."

>>56175115
Stupid article, systemd-mount deprecated udev, autofs and polkit a long time ago.

NONE of the packages it got deprecated was Unix

Numbered List of Key Points in C's History

1. Starts with assembler code on EDSAC [3], the Most Godawful Computer on Earth (TM).

2. University orders a watered-down Atlas called Titan/Atlas2. Must wait years to get it and still another year to make it run.

3. Need new language for it plus it was trendy to make new languages for new computers.

4. ALGOL60 [4] had many nice features of languages today but was too theoretical: only existed on paper.

5. Fortran was locked into IBM mainframes and mapped 1-to-1 to their hardware, not Atlas or Titan.

6. Designed CPL language as a real-world version of ALGOL *before* their Titan shipped. CPL had all kinds of features supporting many types of applications, even lambda calculus!

7. Had to use Most Godawful Computer on Earth (EDSAC) to build the CPL compiler.

8. Queued up behind others with snippets of EDSAC machine code testing pieces of it. Predictably, this didn't scale to CPL's size and complexity. Abandoned CPL compiler.

9. New design goal: trim out anything hard to compile from CPL. Naturally eliminates most features for robust and maintainable programming.

10. New design goal: give programmer total control to the point that he or she can do arbitrary stuff in memory. Maps better to Most Godawful Computer on Earth's style of execution and constraints.

and tools sucked. He and Ritchie decided to build a bare-bones version of MULTICS, called UNICS, in assembly focusing on simplicity and performance above everything. Stripped out or changed most features benefiting safety/security, maintenance, and consistency.

15. Around same time, Thompson was trying to get BCPL to work on his similarly-awful PDP-7. Had to trim it further to make it fit. Changed syntax for personal style. That included long-time headaches like going from ALGOL := assignment and = equality to = assignment and == equality. Resulted in B language.

16. The PDP-11 [8] was byte/character-oriented instead of word-oriented. B didn't work well. Ritchie added limited typing to it to support these plus a few other changes. Result was the C language.

17. Rewrote parts of UNIX in C. Others were too hard.

18. Those difficulties led to adding struct's which allowed rest to be re-written in C. Neither C nor UNIX were meant to be portable despite some people's claim it was a "cross-platform assembler."

18. Simplicity of C and UNIX allowed easy porting anyway which started from a year later onward by other people.

19. K&R adds some types and standard I/O. Remained for years the baseline for portable C.

20. Bjourne loves programming in Simula [9]: an ALGOL60 superset with classes and concurrency. Creates C with Classes to bring it closer to Simula.

21. Bjourn adds features from ALGOL68, Ada, CLU, and ML to C w/ Classes to produce C++: a C extension that reduces freedom where sensible but mostly adds features for productive or maintainable programming.

22. ANSI C standard created a superset of C features, including some from C++. Becomes standard style for C programming. Tons more code written this way.

Conclusion(s)

So, there you have it. They started with a great language (ALGOL60) that inspired Go, etc. Needed something ground in reality, leading to similarly great CPL. Hardware and software were so hard to use they stripped it to bare minimum (BCPL). Thompson stripped that to B because his PDP-7 was too limited and added syntax problems purely due to preference. Ritchie added a little to that to get the PDP-11 to work, resulting in C. Added struct's to for more complex data structures. Writing the simple, UNIX in C language caused C to flourish as it did due to social and economic reasons [10]. Eventual standard borrowed a bit from C++. All the C code out there resulted.

Hardware eventually got better than EDSAC, PDP-7, or PDP-11. Language and OS decisions created due to its limitations aren't removed. All of that is extended or worked around instead. UNIX and later C applications have those issues as a result. Result is a mess so huge [11] that it might be impossible to fix.

Conclusion: the worst aspects of UNIX and C were intention design decisions that had nothing to do with what a good, systems language should look like and everything to do with limitations of an EDSAC, PDP-7, & PDP-11.

Conclusion 2: we should've ditched or modified C to look more like ALGOL68 a long time ago. Like Bjourne and Wirth were doing.

Conclusion 3: C and UNIX should be avoided where possible because they're Bad by Design for reasons that stopped applying sometime in the 80's or early 90's.

However, if you're device's hardware is PDP-11 equivalent, then there is a language and OS that are stripped enough to run on it. Might want to consider C and UNIX 1.0 then. ;)

And I'm not talking about IE crashing, but the graphical glitch.

>>56175069
Explorer not updating the background after it's been drawn over.
Effectively making the window "stay" in that spot. If you'd hide it, it'd look like it was exactly where you left it, even thought it's not there.
It's easy to recreate by accident when working with graphic stuff

>>56175069
It's time to move on from Windows 98, friend

File: 1471007438949.jpg (62KB, 690x460px) Image search: [Google]

62KB, 690x460px

>smartphone

File: 1471466579038.png (45KB, 349x400px) Image search: [Google]

45KB, 349x400px

sgs4

>>56175056
His nickname is RMS which stands for Richard "Macintosh" Stallman, and he obviously uses iPhones only.

>>56175055
>>>/v/

just delete it
corporate cucks are shameless and will steal /sell your info in a heartbeat

File: Screenshot_20160820-233048.png (644KB, 1080x1920px) Image search: [Google]

644KB, 1080x1920px

>>56175210
Looks like I found a better solution

Open the beginner shit and go to page 20

start a project and learn along the way

>>56175013
Stop and pickup java

>>56174897
Hey, I think that's the PSU I use!

Why not go for a modular PSU, like https://www.amazon.com/EVGA-SuperNOVA-Modular-Warranty-110-B1-0750-VR/dp/B00K85X23O/, which has 6 SATA ports.

Also, the line is going to be "split" at some point, no matter what. There just isn't physical space on the PSU, otherwise. If there's a voltage drop due to splitting, it's probably not due to the split itself (unless you have over 4 devices connected to a single cable, maybe), but simply a symptom of an underpowered PSU in general.

>>56174897
>the voltage drop from splitting power
You don't know how electricity works.

Fuck off.

>>56174952
nvm, the one I linked only has 3 SATA ports. Should still be plenty for 12 connectors, though, depending on the power draw of the things you connect.

hahaha no

you need at least latest xeons and 2x them too with dual processor mobo, retard. that MIGHT be just and just enough for your stuff

>>56174855
Yes, CPUs stopped getting faster since sandy bridge (just more energy efficient)

File: 1470777195434.jpg (156KB, 640x656px) Image search: [Google]

156KB, 640x656px

Totally unusable. You need the power that comes from INTEL'S latest and FASTEST microprocessors. Intel's first 10-core processor for desktop PCs is the ultimate tool for delivering unrivaled performance and is our most powerful desktop processor ever. Whether you're gaming, exploring virtual reality, or creating fabulous content, the Intel® Core™ i7 processor Extreme Edition gives you the computing power you need to do it beautifully.
Because the only thing more amazing than Intel® technology is what you can do with it.

There's something wrong with your linker bro.

>>56174866
the problems seem isolated to Qt so far
there's some software marketed to fixing this, but they charge me. i mean i'll look into fixing it but still

i'd rather not use visual studio, think i'll end up using some obscure one . . .

is there literally no alternative