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

>>61555461
Robot please

>>61555461
Just turn on the Legacy CAPTCHA.

Or buy a 4chan pass.

File: bane feel.png (89KB, 604x694px) Image search: [Google]

89KB, 604x694px

>watch this silly commercial
>the Rock hijacks a domestic flight to Akron, Ohio
>he says it's going to Rome now
>mfw aircraft only carry enough fuel to reach their destination

What did Apple mean by this?

>>61555390
>Does anyone here use botnet assistants?

No. No

>>61555390
no I'd feel like an idiot talking to my phone

>>61555272
>AMD

No, get a better processor, such as the newest line of i7 processors from Intel

you have a tiny penis and smell like raisins LOL

>>61555272
what's ramdac

4chan

Any for profit website.

anontalk

>>61555028
>I've never owned a phone before
??????

>>61555028
Get a iPhone. It's perfect for tech illiterate people.

underage b&

>>61554961

I certainly would recommend it.

I had a table that just would not lie flat on the floor. This book was perfect to fit under one leg, removing ten pages at a time until the table was as steady as a rock.

10/10 would recommend.

>>61555208
wow you're very inteligent

Head First Java 2E is excellent. Dont worry about it being published in 2005, thing s have been added since not changed. Covers all the important stuff and from there check out Libgdx for games

abandonware

>>61554786
debian/devuan with task-xfce-desktop

>>61554786
Debian

>>61554688
curl -O https://i.4cdn.org/g/1500990472166.jpg

:^)

>>61554750
That's scripting and not a programming language

>>61554777
>Goes from "favorite language" to "programing language"
Of course

>>61547947
>>61547947
>>61547947
Wrong prev link

imo i think that guy single handedly killed any chance that many of us had getting into hdb.

That's not on Android.

This reminds me of Vista. Especially as it matured, Vista was fine. The problem was with device manufacturers shoe-horning it onto devices WAY below the specs it needed. I wouldn't be surprised to find that you're running into the same issue with your manufacturer.

you know, you could try using a recent version of android on a phone from this decade
becuase
>400x800
>4GiB of ROM
tell me you're using a samsung shitphone with outdated, horrible touchwiz and android 5.1 at best

>>61554672
SD card Loser. Don't have a slot well you shouldn't have gotten a low storage model. Also whats the point of this thread.

>I know how to fix but I still I want to bitch and let /g/ know

The second big problem: Attack Surface

On a hardened system without systemd, you have at most one root-privileged process with any exposed surface: sshd. Everything else is either running as unprivileged users or does not have any channel for providing it input except local input from root. Using systemd then more than doubles the attack surface.

This increased and unreasonable risk is not inherent to systemd's goal of fixing legacy init. However it is inherent to the systemd design philosophy of putting everything into the init process.

RED HAT PAYING DEBIAN TO FORCE SYSTEMD

Systemd is not an init system!!
If someone characterizes systemd as an “init system,” you may safely assume that s/he is either utterly clueless or deliberately obfuscating the discussion. Calling systemd an init system is like calling an automobile a cup holder. Not even Lennart Poettering pretends that systemd is anything but the “Core OS” (sic).

What systemd is is an effort to re-create large portions of existing userspace (including login, job scheduling, and networking, just to name a few) inside a single process traditionally reserved for the sole purpose of starting *nix userspace. (Just in case it isn't clear, there is a huge difference between starting userspace (init) and being userspace (systemd).)

At the end of the day, how one perceives this re-creation of existing userspace strongly influences one's reaction to systemd. There are plenty of perfectly legitimate reasons to be troubled by this re-invention of the wheel; they range from the philosophical and aesthetic, to the technical and mechanical, even the purely political and brutally practical.

And that's part of the problem when folks start to “debate” systemd. Very few folks have the chops to think about, much less talk about all of these areas simultaneously. As a result, the discussion becomes fractured and disjointed, in what is literally the textbook definition of bikeshedding. Suddenly, a talking head who's never written a line of code in his/her life offers up an authoritative-sounding-but-utterly-bogus opinion on systemd's maintainability. Add in the fact that folks on both sides (including Poettering himself) act as if name-calling is a perfectly good substitute for empirical evidence, and the “debate” becomes indistinguishable from white noise.

Full story:
http://forums.debian.net/viewtopic.php?f=20&t=120652&p=570371

Linus Torvalds bashing systemd developers for making kernel developers work around their problems

mailing message:

>Key, I'm f*cking tired of the fact that you don't fix problems in the code *you* write, so that the kernel then has to work around the problems you cause.

>Greg - just for your information, I will *not* be merging any code from Kay into the kernel until this constant pattern is fixed.

>This has been going on for *years*, and doesn't seem to be getting any better. This is relevant to you because I have seen you talk about the kdbus patches, and this is a heads-up that you need to keep them separate from other work. Let distributions merge it as they need to and maybe we can merge it once it has been proven to be stable by whatever distro that was willing to play games with the developers.

>But I'm not willing to merge something where the maintainer is known to not care about bugs and regressions and then forces people in other projects to fix their project. Because I am *not* willing to take patches from people who don't clean up after their problems, and don't admit that it's their problem to fix.

>Kay - one more time: you caused the problem, you need to fix it. None of this "I can do whatever I want, others have to clean up after me" crap.

http://www.phoronix.com/scan.php?page=news_item&px=MTY1MzA

Don't fuck with farmville.
Smart move by Firefox.

>>61554649
what the fuck yo

>doesn't even have asynchronous drawing

Wewest of lads

File: 1471863360622.png (199KB, 439x392px) Image search: [Google]

199KB, 439x392px

>>61554623
>b-b-b-b-b-b-but muh drivers
sorry aymed, this is the end of the ride
leave gpu design to real men

>>61554623
Make it so the top rx Vega card is sub $400 and I'm sold. I never held hope AMD's new cards would even touch the 1080ti.

>>61554652
Don't worry. Now that AMD is pretty much dominating the CPU market in every regard against Intel and the profits are going to be rolling in, they can devote more money, time, and effort to their graphics card lines.

YES FUCKING DIE AMD!!!

I'm so glad AMD Is bound to go bankrupt from Vega fiasco,

>>61554621
>Implying

>>61554451
dont visit sites that contain malicious content nigger

>>61554459
There's no website with malicious content, Telstra is retarded.

>>61554451
>using telstra
>ever
You fucked up m8