In pic related is a mess of logic gates I'm creating as part of my bachelor's thesis. I'd like a more visually appealing way to present it. I've been using Visio. Does anyone know some nice way of handling large amounts of logic gates?
>inb4 ">2016 >using Visio"
Isn't the entire point to be like HyperThreading and interleave instructions on a clock-by-clock (ns) basis and not some 0.1ms crap?
Simultaneous Multi-threading (called hyperthreading by intel) is meant to allow for the simultaneous execution of 2 instructions from 2 threads on the same core during the same clock cycles.
This is simply driver controlled temporal multi-threading with some hacks thrown in for good measure.
I've decided to finally learn Linux and give it a shot. I plan on duel booting it on my spare HDD. I'm starting to use cryptocurrency again and prefer something more secure than windows. As new user, where would be a good OS to start?
Depends on what your intentions are. If you want to learn you want a distro that is not based on anything (debian, gentoo/funtoo, slackware, arch, fedora,...) because the documentation is usually better. If you want it to just werk and be secure ootb I think fedora is the one for you but it doesn't have the amount of packages debian for example offers.
How reattach integrated processor for coding in java
how are you supposed to even hold this piece of shit? it literally doesn't have bezels, your fingers and palm are just going to issue a thousand different inputs and fuck everything up.
You have to add csse to fully eliminate the chance of error inputs and easier typing on edge because too thin bezels. Know this from experience.
Genius design samsung!
Previously on: >>54564996
Welcome to /flt/. We are always open to users of all levels, including absolute beginners.
There are four ways to try Linux, you can:
0) Install a Linux OS on a VM (Virtual Machine/VirtualBox) for "safety purposes"
1) Use the Live ISO directly without installing anything, that way, you can get a "full Linux experience".
2) Dual-boot Linux with Windows/Mac (recommended if you want to learn more about Linux)
3) Go balls deep and overwrite everything...
Comment too long. Click here to view the full text.
I installed SteamOS on a VM and shorty after booting I get a splash screen, some retarded audio like water dripping and then the screen just goes black.
I figure it's a fuckup with the video drivers, but online solutions point to picking recovery mode with problem.
Problem: No grub in this distro, it goes direcly to the splash screen.
When I try to swtich to a tty within the captured VM it switches my main Arch tty instead.
Anyone have any ideas?
The image checksum is fine. I was to get Grub to pop up by just spamming the reset button somehow. Weird. I got into recovery mode, but now it's just stuck at the splash screen.
Is it worth trying to reinstall?
I'm actually crying right now. I've just wasted 10 minutes of my life trying to get this piece of shit to draw a colored rectangle border to highlight a fucking paragraph. Why the fuck didn't I just use Paint.NET in the first place? Use FLOSS that respects your freedom they said. I hope every single one of you GIMP shills die a horrible death. FUCK. YOU.
What are WE (/g/, a board composed mainly of Apple fans) expecting from WWDC?
What do you do if you have to transfer files to and from a phone but the port doesn't work and it doesn't have removable storage?
What is /g/'s opinion on iWork? Is it better than libreoffice or msoffice? IMO it's the best office suite and has the best compatibility with MS office.
office suites are technology
Now that Moot is working for Google, what Technology related things do you think he is doing at his new job right now?
There you go. Distro-agnostic linux has a proper icon now. Stop using Tux.
Looks like a fucking Pokemon ball.
Tell me /g/, what OS is on Snotty Boy's computer?
>have to spend 2 hours charging it
>pop in a new battery
>go from 0 to 100 real quick
I'm familiar with proving big oh, etc. but I haven't came across any resources that provide a general rule of thumb for analyzing program complexity of actual code.
if someone asked me what the run time of an arbitrary program is I'd like to know how to figure it out.
Any resources that explain this or any general rules of thumb?