because 99% of the time it was just a flat out lie.

What I don’t understand is why they lie about something directly causal to the resolution.

Yep, that one where the person on the peak starts lecturing you in abstract terms about trying the simplest hypotheses and such, while you are trying to solve their problem.

I know the philosophy part that asshole is talking about, only he has no bloody clue which part is simple and which is not here.

It was a hang port on a switch in that case.

People who write screen broke shouldn’t be working with technology more advanced than a shovel

Shovel gay, pen have, paper end, rock good.

Google some sites, visit some empty IRC channels, dream of the future for a bit, then turn it off

I’m using ipv6 when I occasionally connect to Yggdrasil.

And I think I’ll use ipv6 if we ever need to build a new earthnet.

It’s a fine technology.

May have something to do with computers as they exist being defined by male psychology. Well, it’s understandable why swords, guns, rockets are, and same with computers.

Basically sending instructions to change state. I don’t know how can a computer exist which doesn’t work like this and is still usable for the humanity, but this seems to be psychologically a bit more of a male thing. Maybe there’s nothing problematic for women but aesthetics there.

If it’s something deeper, then maybe some analog optical\quantum\whatever computers of the future will push us to change paradigms for some drastic change in efficiency. And maybe those new paradigms will be more appealing to women.

Which year it was? I think I had working synchronization between Gajim, Psi+ and Dino. Don’t remember if Conversations fits into this list. There’s a XEP for this supported by them so it should work.

XMPP is modern XMPP replacement.

Had a nice TV from that company. It was really long ago, though, and the terribly bright blue indicator of it being on I didn’t like, especially when using as a PC monitor.

I happen to be a Firefox user

I happen to be a former conkeror user, which was based on XULRunner, which Mozilla dropped, just like other ways to use their engine for other browsers.

But I could use pre-Australis Firefox.

Only then their experiments on people with UI design happened.

And yes, Mozilla as an organization has objective flaws. Their treatment of the SeaMonkey project (now separate) has not been good as well.

I personally just don’t like people calling it AI. It’s not.

I remember that what you are describing was already present in the “open web” of old.

You’d come to some place “openly”, but then (in case of RP forums)

1. until you’d write a long character description and discuss it with mods for long, you wouldn’t be allowed to post in most parts of that forum, and

2. until you had chatted over ICQ with a few people from that forum and knew who they are and they knew who you are, you wouldn’t be really welcome, people would just ignore your posts.

You would come to a place quite socially, not unlike IRL meetings. It wouldn’t be FB or Google confirming your registration and giving you right to post, it would be a real person you were going to communicate with later.

And maybe I’m not that asocial\autistic\etc, if that was fine with me back then and what’s now isn’t. Maybe I’m just afraid of silent eyes and silent hands managing my social interactions, which is sane.

It wasn’t really IE-only. People sort of could use Netscape, and then Mozilla, and then Firefox. And Opera which wasn’t free.

And it was so fast, awww. And had a built-in BitTorrent client which didn’t suck balls and didn’t feel excessive.

And all that caching.

What I don’t get is why hasn’t there been a split yet. Not like Seamonkey, but from major developers of FF.

Sorry, I don’t remember what I used then as a tutorial, possibly nothing, and I don’t write assembly often, it was just an opinion based on the experience from the beginning of my comment. That said:

You have call and return, so you can use procedures with return. You have compare and conditional jump instructions. And you have timers and interrupts for scheduling. That allows for basic structure.

You split your program functionally into many files (say, one per procedure) and include those. That allows for basic complexity management.

To use OS syscalls you need to look for the relevant OS ABI reference, but it’s not hard.

So all the usual. Similar to the dumber way of using C.

In general writing (EDIT: whole programs, it’s used all the time in codecs and other DSP, at the very least) in assembly languages is unpopular not because it’s hard, but because it’s very slow.

They just have understanding of correct criteria of financial success, since they, eh, work with finances.

Well, I only wrote simple exercises in Intel assembly in uni, but there were more of those with AVR assembly.

You can structure things nicely and understandably if you want.

It’s an acquired skill just like many others. Just today writing something big fully in assembly is not in demand, so that skill can usually be encountered among embedded engineers or something like that.