[QUOTE=thefreemann;52473485]I'm really not sure at this point, not having any actual hands-on experience in either, I have an interest in both honestly, what would either route entail? I'm guessing the latter would require some fairly strong programming background?[/QUOTE]
Well the former is what a majority of your upcoming classes will cover, I'd also recommend taking a microelectronics class (Which covers stuff like diodes/transistors in good detail) to really get your feet wet.
If those classes appeal to you then you can really get into nitty gritty low level electronics. Skills you ought to pick up (whether it be through classes or not) if you go this path are learning how to solder, working with circuit simulators (See OP for LTSpice) and a few more things should you really go into the rabbit hole. Later on you should pick up working with PCB CAD/Schematic software like Altium, EagleCAD, KiCAD or DipTrace (as well as learning the ropes for designing PCBs).
The latter would indeed require a fair bit of programming knowledge, usually that encompasses having a good grasp on C/C++ & python (Atleast that's what the guys on my robotics team use). C/C++ is used quite heavily for both low level microcontrollers and high level stuff like RPis (I'd recommend picking up your own Arduino kit for personal use and learning). For CV look into OpenCV, its quite friendly as far as computer vision is concerned. Also your digital logic design class might go into VHDL (which is the language used for programming programmable logic devices) which is less used in robotics but is highly used in industry (Look up FPGAs, ASICs & PLCs). If you can program a PLC and have good problem solving skills you are guaranteed a fairly well paying job at any manufacturer.
Ideally its nice to have atleast a little bit of knowledge/skill from both disciplines, really helps later on down the road.
[QUOTE=LoneWolf_Recon;52474350]Well the former is what a majority of your upcoming classes will cover, I'd also recommend taking a microelectronics class (Which covers stuff like diodes/transistors in good detail) to really get your feet wet.
If those classes appeal to you then you can really get into nitty gritty low level electronics. Skills you ought to pick up (whether it be through classes or not) if you go this path are learning how to solder, working with circuit simulators (See OP for LTSpice) and a few more things should you really go into the rabbit hole. Later on you should pick up working with PCB CAD/Schematic software like Altium, EagleCAD, KiCAD or DipTrace (as well as learning the ropes for designing PCBs).
The latter would indeed require a fair bit of programming knowledge, usually that encompasses having a good grasp on C/C++ & python (Atleast that's what the guys on my robotics team use). C/C++ is used quite heavily for both low level microcontrollers and high level stuff like RPis (I'd recommend picking up your own Arduino kit for personal use and learning). For CV look into OpenCV, its quite friendly as far as computer vision is concerned. Also your digital logic design class might go into VHDL (which is the language used for programming programmable logic devices) which is less used in robotics but is highly used in industry (Look up FPGAs, ASICs & PLCs). If you can program a PLC and have good problem solving skills you are guaranteed a fairly well paying job at any manufacturer.
Ideally its nice to have atleast a little bit of knowledge/skill from both disciplines, really helps later on down the road.[/QUOTE]
Thanks for answering my question in depth, appreciate it. If I decide to pursue the latter, am I going to have competition with Computer Science majors though?
[QUOTE=thefreemann;52475230]Thanks for answering my question in depth, appreciate it. If I decide to pursue the latter, am I going to have competition with Computer Science majors though?[/QUOTE]
Not necessarily, CS are still quite a large swathe including designing/working on OSs, High Performance Computing (Big Data stuff), etc. And only a small chunk will be working on machine intelligence or neural networking.
If I could also chip in; make some things!
You can always find projects which use a mix of skills. Personally I find I retain knowledge much better if I apply it as I learn it. If possible, I like to find projects which mix the things I'm learning about at uni at the moment, to consolidate.
Something I had a great time with early on was making a multimeter: some basic analogue design, some embedded software and some board layout.
Something like an Arduino, or inexpensive clone, is great for getting your feet wet, and will remain a useful tool for a long time afterwards (especially once you stop using their shitty software stack).
You will find uni easy if you keep doing projects in the background.
[URL="https://facepunch.com/showthread.php?t=1437734&p=52470816&viewfull=1#post52470816"]A little crossposting here.[/URL]
[t]http://i.imgur.com/88J4naj.jpg[/t][t]http://i.imgur.com/BxCHz25.jpg[/t]
So I bought this CI-94 the other day at a thrift store. But it seems to be accepting 5p DIN input. Pentium pointed out to me in the Thrift thread that [URL="http://www.amateurengineer.com/?p=623"]someone just made an adapter for it to BNC.[/URL]
I am still a bit beginner so I have a bit trouble identifying which pin to use on the DIN plug. Would anyone maybe be able to help? Should I just try probing the pins until lucky? :v:
And another little question. If it is a 5p DIN input and only ground and a single pin is used, would anyone know what the other pins are used for? It seems kind of weird just to have random pins for nothing.
[QUOTE=Van-man;52478036][url]https://www.tech-n-hack.net/2016/05/making-a-din-to-bnc-adapter-for-the-c1-94[/url] ??[/QUOTE]
I HAVE NO IDEA WHY I AM SO HORRIBLE TO GOOGLE BUT THANK YOU
[editline]17th July 2017[/editline]
I have been searching for C[B]I[/B]-94 all the time lol. It is C[B]1[/B]-94
[QUOTE=Jalict;52478022][URL="https://facepunch.com/showthread.php?t=1437734&p=52470816&viewfull=1#post52470816"]A little crossposting here.[/URL]
[t]http://i.imgur.com/88J4naj.jpg[/t][t]http://i.imgur.com/BxCHz25.jpg[/t]
So I bought this CI-94 the other day at a thrift store. But it seems to be accepting 5p DIN input. Pentium pointed out to me in the Thrift thread that [URL="http://www.amateurengineer.com/?p=623"]someone just made an adapter for it to BNC.[/URL]
I am still a bit beginner so I have a bit trouble identifying which pin to use on the DIN plug. Would anyone maybe be able to help? Should I just try probing the pins until lucky? :v:
And another little question. If it is a 5p DIN input and only ground and a single pin is used, would anyone know what the other pins are used for? It seems kind of weird just to have random pins for nothing.[/QUOTE]
SCOPE BROOOOS
[t]https://my.mixtape.moe/bqvrmz.jpg[/t]
[QUOTE=thefreemann;52473485]I'm really not sure at this point, not having any actual hands-on experience in either, I have an interest in both honestly, what would either route entail? I'm guessing the latter would require some fairly strong programming background?[/QUOTE]
I keep forgetting to check up on this thread, as despite not doing much EE work anymore I always find it interesting. Regardless, I can give some extra input on what to prepare for a job - I work in the space industry for a small (but growing fast) R&D firm, and one of our biggest divisions is based on robotics and lots of fancy EE work.
- FPGAs and PLCs are a [I]really[/I] good thing to have experience in. We use them tons for SDR stuff which isn't what you're interested in, but its a great thing to have going for you when applying for internships
- Get plenty of C/C++ experience. Choose your reference books carefully: some forward outdated techniques despite claiming modern techniques. Further, the kind of programming you'll do is a bit different than the C++ I use but do be very careful choosing books/learning material. There is a [I]tremendous[/I] quantity of utterly shit C++ resources. Practice compliance to various code safety standards. I think the JPL C guidelines are just generally great guidelines for embedded programming, but the MISRA stuff goes further (but I can't say its fun)
- Play with Python a bit, and probably MATLAB too if you can manage. I despise MATLAB but it sees lots of use still, unfortunately.
- For computer vision, maybe see if you can get some experience working with something like CUDA or other GPGPU systems: those see some usage in robotics. If you have a Nvidia card, CUDA will more than suffice. If not, OpenCL is scary and gross so maybe try SYCL (linux only for now, though). The key is just learning to understand how weird GPUs are, and how to program with them in mind. The SIMT programming model is hard to get used to. Graphics/GPU stuff is my passion, so I could babble about this for ages tbh but to tldr it: GPUs are fucking weird, man.
- As LoneWolf_Recon mentioned, learn to solder, work with circuit simulators, and consider practicing board design (or at least using board design software). Brush up on ESD safety, at least slightly, and practice those habits too. You don't want to be the intern ruining production hardware due to an ESD issue!
Its hard to give more advice about CV stuff and what to practice for that as we don't do that at my work - I'm not sure how common Nvidia's little Jetson boards are, but a number of my fellow students at Uni in my CUDA research course used them to play with machine vision setups in their cars. The power of the things was really impressive, but given their power draw and Nvidias lack of background in real-time systems and such i'm not sure if the industry uses them. I'm hoping to get a full-time job here, actually. Probably in our radios division, instead of the additive division that I'm currently in. Additive has no need for C++ devs, and radios didn't either - until we recently switched to using C++ for our radio stuff. Its a lighter and less feature-rich C++ implementation in terms of the standard library, but it means I might have a shot at a job. Not exactly the kind of job I want for life, but it'd be interesting work on hardware that [I]will[/I] be on spacecraft and it'd be a good way to save funds before possibly returning to school in a few years.
[QUOTE=paindoc;52478382]I keep forgetting to check up on this thread, as despite not doing much EE work anymore I always find it interesting. Regardless, I can give some extra input on what to prepare for a job - I work in the space industry for a small (but growing fast) R&D firm, and one of our biggest divisions is based on robotics and lots of fancy EE work.
- FPGAs and PLCs are a [I]really[/I] good thing to have experience in. We use them tons for SDR stuff which isn't what you're interested in, but its a great thing to have going for you when applying for internships
- Get plenty of C/C++ experience. Choose your reference books carefully: some forward outdated techniques despite claiming modern techniques. Further, the kind of programming you'll do is a bit different than the C++ I use but do be very careful choosing books/learning material. There is a [I]tremendous[/I] quantity of utterly shit C++ resources. Practice compliance to various code safety standards. I think the JPL C guidelines are just generally great guidelines for embedded programming, but the MISRA stuff goes further (but I can't say its fun)
- Play with Python a bit, and probably MATLAB too if you can manage. I despise MATLAB but it sees lots of use still, unfortunately.
- For computer vision, maybe see if you can get some experience working with something like CUDA or other GPGPU systems: those see some usage in robotics. If you have a Nvidia card, CUDA will more than suffice. If not, OpenCL is scary and gross so maybe try SYCL (linux only for now, though). The key is just learning to understand how weird GPUs are, and how to program with them in mind. The SIMT programming model is hard to get used to. Graphics/GPU stuff is my passion, so I could babble about this for ages tbh but to tldr it: GPUs are fucking weird, man.
- As LoneWolf_Recon mentioned, learn to solder, work with circuit simulators, and consider practicing board design (or at least using board design software). Brush up on ESD safety, at least slightly, and practice those habits too. You don't want to be the intern ruining production hardware due to an ESD issue!
Its hard to give more advice about CV stuff and what to practice for that as we don't do that at my work - I'm not sure how common Nvidia's little Jetson boards are, but a number of my fellow students at Uni in my CUDA research course used them to play with machine vision setups in their cars. The power of the things was really impressive, but given their power draw and Nvidias lack of background in real-time systems and such i'm not sure if the industry uses them. I'm hoping to get a full-time job here, actually. Probably in our radios division, instead of the additive division that I'm currently in. Additive has no need for C++ devs, and radios didn't either - until we recently switched to using C++ for our radio stuff. Its a lighter and less feature-rich C++ implementation in terms of the standard library, but it means I might have a shot at a job. Not exactly the kind of job I want for life, but it'd be interesting work on hardware that [I]will[/I] be on spacecraft and it'd be a good way to save funds before possibly returning to school in a few years.[/QUOTE]
Thanks, I'm already very comfortable using Python actually, and I'm trying to learn C. C/C++ are quite similar right? Also is it essential to be able to operate in Linux? I've heard that it's a desirable skill for robotics, or does it vary from team to team?
[QUOTE=thefreemann;52479854]Thanks, I'm already very comfortable using Python actually, and I'm trying to learn C. C/C++ are quite similar right? Also is it essential to be able to operate in Linux? I've heard that it's a desirable skill for robotics, or does it vary from team to team?[/QUOTE]
Syntactically yes, they're both the same. (I'm coming from an intermediate level of skill with C/C++). The only really difference is that C++ includes stuff like the STL & Classes/Vectors/Strings. Kinda alot of bonus stuff that makes your life alot easier. Keep in mind alot of this bonus stuff (save for strings) won't be available on low level stuff like Arduinos.
There's also some very nit picky differences that I don't know the details of (I only use C++ for microcontrollers and simple windows programs), paindoc could probably fill you in on the details.
[QUOTE=thefreemann;52479854]Thanks, I'm already very comfortable using Python actually, and I'm trying to learn C. C/C++ are quite similar right? Also is it essential to be able to operate in Linux? I've heard that it's a desirable skill for robotics, or does it vary from team to team?[/QUOTE]
Linux stuff would probably involve using ROS - maybe give that a look.
If you want to learn more C++ stuff - "C++ Primer". Latest edition you can find. Modern C++ is about making life easier - and there are still elements of it you can use in embedded systems. Usually want to avoid things like vectors though - despite being wonderfully pythonic, they allocate memory at runtime like crazy and thats less than ideal. That being said, C++ now has things like std::array with a defined compile-time size. Safer to use, integrates with the AWESOME std::algorithm set of stuff, and works with iterators (which are also great! and fast!). There's a lot of other details too, but at the least competent C++ can be safer and easier to write than C while still maintaining high C-equivalent speeds - things like std::unique_ptr are great and eliminate memory leaks at no cost, and as mentioned things like std::array give you fast arrays but still allow you to use algorithms that have been implemented by people more competent than most programmers.
LoneWolf_Recon covered it though: C++ is truly in many ways C ++ a shitload of useful and helpful stuff, but modern C++ looks far removed from C. Consider [URL="https://gist.github.com/MathiasPius/9ce2f0a7cc50a4643a4a4d8fce4011f4"]this example[/URL] of Run-Length encoding I got from another FP'er and tell me it doesn't look damn near Python.
You'd be surprised how easy it is to work with Linux, tbh. I enjoyed using Ubuntu on my Surface Pro a ton. If there was Visual Studio for Ubuntu I'd probably use it for all of my dev work - Ubuntu is just generally easy to play with for development tasks
[editline]17th July 2017[/editline]
There are a lot of complexities to C++ though, and thats why its so tough. Its a great language and I [I]adore[/I] it and writing it, but its very feature dense and has quite the learning curve. The learning curve isn't due to difficulty, imo, but due to the quantity of things there are to learn about it.
I'd say try to get experience programming C to the aforementioned [URL="http://lars-lab.jpl.nasa.gov/JPL_Coding_Standard_C.pdf"]JPL guidelines[/URL] to polish good embedded programming habits, but also try to play with Modern C++ when you can
[editline]17th July 2017[/editline]
I started programming by programming in C for embedded systems, and have moved far from that since then. That being said, many of the things I learned doing what I started with have helped me in C++: others haven't, and that was most apparent in my failure to use C++ (modern or otherwise) features. Its not hard to make the transition or to blend your knowledge, though.
Anyone know how to dismantle a 3 phase tranformer or if it's possible to unbolt the frame holding the cores together? It's currently in the back of my car making it look like a low rider from the weight alone. No way in hell I can lift a 300lb hunk of iron when I can barely move it in the back of my car alone.
[QUOTE=Sombrero;52490224]Anyone know how to dismantle a 3 phase tranformer or if it's possible to unbolt the frame holding the cores together? It's currently in the back of my car making it look like a low rider from the weight alone. No way in hell I can lift a 300lb hunk of iron when I can barely move it in the back of my car alone.[/QUOTE]
Unless you're in the brevard or orlando area..
And anything comes apart if you try hard enough!
[QUOTE=Sombrero;52490224]Anyone know how to dismantle a 3 phase tranformer or if it's possible to unbolt the frame holding the cores together? It's currently in the back of my car making it look like a low rider from the weight alone. No way in hell I can lift a 300lb hunk of iron when I can barely move it in the back of my car alone.[/QUOTE]
I don't suppose you have pictures of said transformer?
I've been tinkering around with an Intel 8031-based toy keyboard, and the demo tunes are fucking stuck in my head.
[t]http://i.imgur.com/TNcUVHL.jpg[/t]
Finally starting to assemble some PCBs I designed a while ago; My first ever SMD boards, mostly in 0805/SOIC. This is a 5 IR sensor board for a maze robot. Unfortunately, because I'm a smart cookie, I didn't realise the AVR on the board(tiny40) is a TWI chip, not ICSP; despite specifically reading the datasheet at least once to make sure it was ICSP capable. :goodjob:
[t]http://i.imgur.com/fUnvoae.jpg[/t]
Enter the DIY piggyback programmer. After spending a while tracking down a 0.25mm 3d printer nozzle in the lab, programming was achieved. The actual plastic part fits really well on the chip - it 'clips' on nicely. The pogo-pins are thin pieces of copper salvaged out of a flat flex connector, and don't really do the job well, needing constant pressure from a few fingers to keep good contact.
On a completely different topic, would any of you lovely souls have half a fucking idea how Biometric sensors talk to android devices over bluetooth?
Specifically, my project goal is to DIY a bike cadence meter. COTS solutions all seem to communicate over bluetooth or ANT+, and I'm having absolutely 0 success in tracking down any information on the protocol used. As much as I'd like to buy one and buspirate it, I'm rather cash strapped at the moment :pudge:
I'd imagine this has been asked before, and there's a book or something, but I've got a dumb question. [i]What is electricity?[/i] What are watts/volts/ohms/amps? Is there a guide for simple stuff such as that so I can at least get a grasp?
[QUOTE=VeXan;52541348]I'd imagine this has been asked before, and there's a book or something, but I've got a dumb question. [i]What is electricity?[/i] What are watts/volts/ohms/amps? Is there a guide for simple stuff such as that so I can at least get a grasp?[/QUOTE]
The absolute basic bare gist of it (and I'll no doubt have people add on to this or correct me) is this:
Electricity is the movement of electrons along a conductor.
Watts are a measure of power used, not exclusive to electricity. Watts = Voltage x Amps.
Amps are a measure of how many electrons are being moved through a conductor. A given amount of electrons moving through a section of a conductor ( Amps = Voltage/Resistance (Ohms)
Ohms is a measure of resistance to the amount of electrons that can move through a given conductor. Resistance (in Ohms) = Voltage/Amps.
Voltage is an electric potential between two points in a circuit. Think of it like pressure in a compressed air tank. In an air tank, you have a given pressure (let's say 50 PSI) compared to the ambient pressure of our atmosphere (a little less than 15 PSI at sea-level), so there is what's called [I]potential difference[/I]. Open the valve on the tank, and this difference will move air from the high pressure side (the tank) to the lower pressure side (the atmosphere), and you can even have the air do something along the way (like power a tool) before it's released into the atmosphere. Same thing with voltage, more or less. The more voltage ("pressure") you have on one side (the supply side), the more potential you have to move electrons. Voltage = Resistance (in Ohms) * Current (in Amps).
There are a myriad of websites with documentation on the subject, as well as various Youtube videos that explain it in levels ranging from absolute layman to the more advanced physics level.
[QUOTE=Zero-Point;52541468]The absolute basic bare gist of it (and I'll no doubt have people add on to this or correct me) is this:
Electricity is the movement of electrons along a conductor.
Watts are a measure of power used, not exclusive to electricity. Watts = Voltage x Amps.
Amps are a measure of how many electrons are being moved through a conductor. A given amount of electrons moving through a section of a conductor ( Amps = Voltage/Resistance (Ohms)
Ohms is a measure of resistance to the amount of electrons that can move through a given conductor. Resistance (in Ohms) = Voltage/Amps.
Voltage is an electric potential between two points in a circuit. Think of it like pressure in a compressed air tank. In an air tank, you have a given pressure (let's say 50 PSI) compared to the ambient pressure of our atmosphere (a little less than 15 PSI at sea-level), so there is what's called [I]potential difference[/I]. Open the valve on the tank, and this difference will move air from the high pressure side (the tank) to the lower pressure side (the atmosphere), and you can even have the air do something along the way (like power a tool) before it's released into the atmosphere. Same thing with voltage, more or less. The more voltage ("pressure") you have on one side (the supply side), the more potential you have to move electrons. Voltage = Resistance (in Ohms) * Current (in Amps).
There are a myriad of websites with documentation on the subject, as well as various Youtube videos that explain it in levels ranging from absolute layman to the more advanced physics level.[/QUOTE]
Thank you, I should look for some of those videos meant for a layman :v:
Hey, industry guys again, to what extent will EE position interviewers ask technical questions? I suppose it varies depending on the position, but for example, an avionics position in aerospace? Should I be sure to brush up on my E&M knowledge?
To be more accurate:
Watts is the power dissipated at any given instant in time, in relation to energy (Joules) 1 Watt is equivalent to 1 Joule per second, energy over time typically uses the Watt-Hour unit rather than joules, [del]so a constant dissipation of 1W will consume 3600Wh of energy (1*60*60)[/del].
Amps is the measure of the rate that charge is moving through a conductor, charge being the Coulomb which is equivalent to 6.241e18 electrons per second, so a current of 1A will move 1C of charge per second, another often used unit is the Amp-Hour which is typically used to define battery capacity, a battery rated for 1Ah can provide a constant current of 1A for exactly 1 hour.
Resistance defines the rate that electrons are able to move through a conductor, zero resistance will result in infinite current and zero power dissipation (in the conductor), the reciprocal unit of resistance is conductance measured in Siemens (or the older Mho) which is frequently used when dealing with very high values of resistance or in transfer conductance of amplifiers.
[b]Edit[/b]
Cocked that right up, 1W is equivalent to 1Wh or 3600 joules, so a 60W lightbulb uses 60Wh of energy or 216kJ over 1 hour, the difference between Watt and Watt-Hour is the former is a measurement at any instant and the latter would be the average over a 1 hour period, for a constant load like a light bulb these would be equal, but for a load that varies these would be different.
[QUOTE=VeXan;52541542]Thank you, I should look for some of those videos meant for a layman :v:[/QUOTE]
One thing that you should know as well is that when we refer to current (say moving from a battery + to -) we're refering to "traditional current" which is the opposite of electrons. These are known as holes, so holes move + to - and electrons move - to +.
[QUOTE=thefreemann;52542004]Hey, industry guys again, to what extent will EE position interviewers ask technical questions? I suppose it varies depending on the position, but for example, an avionics position in aerospace? Should I be sure to brush up on my E&M knowledge?[/QUOTE]
If anything it doesn't hurt to have some practice or actual projects under your belt besides just theory. I.e. for Avionics maybe do a small project in your own time to learn about PID controllers and how to balance them. That way you learn a very important bit of theory for autopilots and have a project to back it up (maybe a self leveling balsa wood glider with arduino control that controls servos adjusting the pitch/yaw of the aircraft and some gyros to give feedback).
Of course that's a somewhat involved project but it never hurts to do it.
[QUOTE=VeXan;52541542]Thank you, I should look for some of those videos meant for a layman :v:[/QUOTE]
Look up a book called "All About Circuits". It's a free series of books (start with the one on DC) by a university lecturer, which is very approachable. It starts by delving into exactly those questions you just mentioned. There used to be a list of these kinds of book in the OP, I'm not sure what happened to it.
[editline]8th August 2017[/editline]
More Xilinx nonsense
[IMG]http://i.imgur.com/bVl64CB.png[/IMG]
ISIM segfaults when it is run without those environment variables being set. You can build and fuse your simulation executable fine, but it won't run.
[QUOTE=r0b0tsquid;52549295]Look up a book called "All About Circuits". It's a free series of books (start with the one on DC) by a university lecturer, which is very approachable. It starts by delving into exactly those questions you just mentioned. There used to be a list of these kinds of book in the OP, I'm not sure what happened to it.[/QUOTE]
I really need to fix up the OP, speaking of would anyone be interested in a discord channel ?
Forrest Mims also does a very nice book, plenty of stuff on youtube as well, I'd recommend watching w2aew, bigclive, eevblog, mr carlson's lab, the signal path, mikeselectricstuff, bunch of lectures on there by MIT and NPTEL if you want more detail.
[QUOTE=Chryseus;52549369]I really need to fix up the OP, speaking of would anyone be interested in a discord channel ?
Forrest Mims also does a very nice book, plenty of stuff on youtube as well, I'd recommend watching w2aew, bigclive, eevblog, mr carlson's lab, the signal path, mikeselectricstuff, bunch of lectures on there by MIT and NPTEL if you want more detail.[/QUOTE]
Discord would be cool, especially now that I'm going into my GPA-killing fundamentals classes ._.
I need people to vent to
Discord channel is now open:
[b][url=https://discord.gg/qDgEFBq]https://discord.gg/qDgEFBq[/url][/b]
But what if I only use IRC? Is there a discord plugin?
Yes there is
You need to set up [url]http://bitlbee.org/[/url] and install this plugin [url]https://github.com/sm00th/bitlbee-discord[/url]
I don't wanna live without bitlbee anymore, it does everything so well!
Like all these normal discord users have a bloated slow electron client - you will have a blazing fast and efficient client in pure c
[url]https://github.com/EionRobb/purple-discord[/url]
For those of us that's stuck on the edge of equilibrium between thinking IRC is for old nostalgic geezers, and that current trend with round avatars and proprietary [I]APP EVERYTHING!![/I] is equally retarded.
Sorry, you need to Log In to post a reply to this thread.
Electrical Engineering V3
