[1:55]

Wikihosting

Name: Anonymous 2017-07-08 13:50

What wiki hosting site you reccomend?
(i'm planning to migrate from reddit wiki, don't need anything fancy: just page history,categories(or tags) and hyperlinks).
The 5 newest replies are shown below.
Read this thread from the beginning.

Name: VIPPER 2017-07-24 20:02

>>49
I prefer hackerjews, but even hackerjews has been going downhill
whenever I browse it I see garbage like this:
Amazon's Whole Foods deal under scrutiny
Host your own contacts and calendars and share them across devices
The Company Behind Many Surprise Emergency Room Bills
Cafeteria workers at Facebook struggle to make ends meet
What happens to digital money if the ICOs never stop?
A Guide to Intermittent Fasting
Learn Ethereum smart contract programming

(Post truncated)

Name: Anonymous 2017-07-24 23:53

>>51
It's been like that for a long time tho

Name: Anonymous 2017-07-25 4:50

1.
Amazon jacked up Prime Day prices, misleading consumers, says vendor (foxbusiness.com)
154 points by buckbova 3 hours ago | | hide | 87 comments
2.
Trust Issues: Exploiting TrustZone TEEs (googleprojectzero.blogspot.com)
31 points by jor-el 2 hours ago | | hide | discuss
3.
How Microsoft Brought SQL Server to Linux (techcrunch.com)
20 points by rusht 3 hours ago | | hide | 4 comments
4.
(Post truncated)

Name: Anonymous 2017-07-25 4:51

>>53
Most of those are technology related.

Name: Anonymous 2017-07-25 7:13

>>51
what's wrong with cryptocurrency-related discussion? I'd like to invest in DubsCoin
Don't change these.
Name: Email:
Entire Thread Thread List
[2:6]

UN*X

Name: Anonymous 2017-07-22 22:48

UN*X

By Alan Filipski


The UN*X brand operating system was writting by two computer science researchers in a closet in the attic of a famous research laboratory (The Labs) in the late 1960s. The authors had complete freedom to design an operating system according to their own wishes without management constraints. This was because everyone at The Labs, including the management, thought they were janitors who spent their time in the closet wringing out mops or something.

The first version of the UN*X brand operating system was a game that simulated the gravitational motion of all known planets and satellites of our solar system. Soon such things as a file system and user procedures were grafted onto it. It ran on a PDP-7 computer that someone had stored in the closet and forgotten about.

Later the authors made the mistake of drawing attention to themselves by asking the management for a larger computer. At this, the management took the operating system and, supposing it to be something of use only to hippies (or closet hippies), sent it University of California at Berkeley.

It may be coincidental, but at the about the same time cases of a peculiar compulsive mental disorder known as Unirexia Nervosa were first noted in San Francisco, Calif. area. The symptoms of this disorder are the interjection of nonsense words such as grep, awk, runrun, and nohup by the victim into his or her speech; the misuse of ordinary words such as cat and lint; and the avoidance of the use of uppercase letters.

Advanced cases of Unirexia Nervosa have been found at many major universities throughout the U.S., where youths with pasty complexions and sunken eyes can be found late at night subsisting on diet pop, glaring fanatically at CRT's, and mumbling about "one more bugs". Since for the most part this malady has been confined to university students, it has not cause great public alarm. But recently there have been reports of regular people contracting the disease, even some who hold otherwise respectable positions in industry. The mode of transmission of Unirexia Nervosa is not known, but it is thought to have something to do with beards.

Members of the UN*X community have developed a novel and effective means of communication with each other. Suppose a user named Athol at Epizootic Systems in Cupertino, Calif., wishes to send an electronic mail message to his friend Elba at Perjorative Systems Inc. in Palo Alto, Calif. Although their computers do not communicate directly, they message may be passed via intermediate links. Athol would merely type:

mail ihnp4!allegra!ucbvax!seismo!decvax!cbosgd!ucbvax!pejor!elba

and then enter the text of his message. This electronic mail would appear at Elba's terminal either within two days of the time it takes to propagate a telephone signal 73 times between the East and West Coasts of the U.S., whichever is greater.

Although many people think the word "UN*X" is an acronym (or even a homonym), the word actually originated in the following manner. When management in The Labs noticed the strange machine running in the closet, they stopped the first technical-looking type they saw in the hall and asked him what it was. As fate would have it, it was not a technical type at all but a member of a lost Australian aboriginal tribe who had been wandering the halls of The Lab for years without drawing attention. The fellow did not understand English and believed they were asking him to haul the computer away. He replied, "UN*X(tm)," which is aboriginal for "Not my job, man." The rest is history.

The different versions of the UN*X brand operating system are numbered in a logical sequence: 5, 6, 7, 2, 2.9, 3, 4.0, III, 4.1, V, 4.2, V.2, and 4.3.

The C programming language is descended from the languages B and BCPL (short for Bucephalus, Alexander the Great's horse). It is a highly structured language. The following structured program, for example, is well-known to all C language programmers, and prints a well-known message at the terminal (try it!):

#define TWENTYNINE 29
int ll, L1, l0, h_1,q,h1,h;
main(){
for(putchar(putchar((h=7)*10+2)+TWENTYNINE);
l0?putchar(l0):!h_1;
putchar (ll),L1==2?ll=' ':0){
L1++==0?(ll=l0=54<<1):
ll=='l'&&L1<3?(ll+=1L|
1L<<1L,l0=0)
:L1==sizeof L1&&ll==' '
?(ll=19+h1):(q-=h1);
L1==5?ll-=8:q&& &
h_1;L1==sizeof ll+2?
(ll+=3):1L;ll==(h<<4)+2
&&L1!=6?(ll=ll-
6):(h1=100L);L1!=1L<<3?q--
:(h_1=ll=h1);
}
printf("%s\n",0);
}


Note the absence of goto statements in the program. Also note how the portability of the program is enhanced by judicious use of the C preprocessor and the sizeof operator. The dereferenced null pointer at the end is used to make sure the output is properly terminated.

The most commonly used UN*X interactive command language is known as the Bourne shell. (This shell was recently completely rewritten and is now available as the Bourne-again shell.) The shell provides a uniform syntax by which the user can interact with the operating system kernel and utility programs. The utility programs in turn accept a uniform syntax of command line arguments and options. Typical examples of utilities are the ar utility, which requires single-letter options that are lumped together in a specified order with an introductory minus sign, before the other arguments; and the find utility, which has multiletter options that cannot be lumped together, each of which must be preceded by a minus sign and which follow any other arguments.

Besides being used interactively, the shell itself may be used as a programming language. Although programs written in shell are slower than equivalent programs written in C, they are shorter and easier to read and debug. For example, to add 1 to a variable a in C one would have to write:

a = a + 1;

or:

a += 1;

or even:

a++;

In shell, one need only write:

a = `expr $a + 1`

where it is essential to have spaces around the + sign to use the $ sign only before the righthand occurrence of the variable a, and to use the backward quote character instead of the common single quote. When UN*X brand operating system programmers want to develop an application quickly, they often use the shell because of this convenient syntax.

Security is a very important issue in the UN*X brand operating system world. The typical UN*X brand operating system source licensee is living in a fool's paradise, little realizing that on the streets of every major city wander broken hackers who would kill for access to kernel source code. These people may be down on their luck, but they are not stupid. As you read these words, there are people who but for lack of a quarter would be whistling uucp protocols at 1200 baud to your modem from a downtown pay phone.

Therefore, the prudent administrator should be aware of common techniques used to breach UN*X brand operating system security. The most widely known and practiced attack on the security of the UN*X brand operating system is elegant in its simplicity. The perpetrator simply hangs around the system console until the operator leaves to get a drink or go to the bathroom. The intruder lunges for the console and types rm -rf / before anyone can pry his or her hands of the keyboard. Amateur efforts are characterized by typing in such things as ls or pwd. A skilled UN*X brand operating system security expert would laugh at such attempts.

The Trojan horse strategy is used in many attempts to defeat the security of a UN*X brand operating system installation. The following scenario is typical: The UN*X brand operating administrator arrives at work one afternoon and finds a new terminal outside the system security area. Since it is better than the current system console, he brings it in to the computer. After a few minutes of use, hordes of cockroaches come pouring out of the back of the terminal, driven out by the heat. The operator jumps up to stamp them out and the intruder has his will with the system.

How can this sort of damage be prevented? The greatest weakness of the UN*X brand operating system is the fact that the superuser root is so powerful. Therefore, an important principle is simple to minimize the use of root. An ingenious way of doing this is to first, without looking, set the root password of the system to some randomly generated string of character. Do not memorize or even look at this string. Now set up the /etc/inittab file with the run level 2 flag that will cause it to demand this unknown password whenever the system is booted. The system is now secure. Log off.

What can a system administrator do if he suspects that some has broken root? Simple. First, at the slightest suspicion that someone has unauthorized access to the superuser capability, immediately seal off the computer room, sound the fire alarm, release inert halon gas into the atmosphere, and activate the automatic sprinkler system. Type "shutdown 0" and cut all circuit breakers to the computer. Physically destroy all magnetic media that have ever been mounted on or associated with the insecure system in any way. Order a new distribution and reboot.

An administrator who is aware of these methods can maintain a sufficient degree of paranoia for most applications.

It has often been said that if God had a beard, he would be a UN*X programmer. While this may be an exaggeration, it is true that UN*X brand operating system is well on its way to replacing the outmoded 10- and 15-year-old operating systems in common use today.

Name: Anonymous 2017-07-22 22:56

God does have a beard, though He uses VAX/VMS.

Name: Anonymous 2017-07-24 1:15

sorry op, your copypasted story was too long

Name: Anonymous 2017-07-25 2:00

I love this

Name: Anonymous 2017-07-25 3:42

Did you write that OP? Else you should give proper credit.
Good stuff tho

Name: Anonymous 2017-07-25 3:47

>>5
First three lines:
UN*X

By Alan Filipski
Don't change these.
Name: Email:
Entire Thread Thread List

Name: S-experiments Lain 2013-09-19 12:02

Serial Experiments Lain
The 5 newest replies are shown below.
Read this thread from the beginning.

Name: Anonymous 2017-07-23 20:53

>>17
Bye lain :(

Name: Anonymous 2017-07-24 12:57

>>17
They missed the part where she talks to herself.

Name: VIPPER 2017-07-24 20:03

>>20
you mean the entire game and ani-meh?

Name: Anonymous 2017-07-24 20:22

>>21
No

Name: Anonymous 2017-07-25 1:50

Holy shit this op made me laugh my ass off
Don't change these.
Name: Email:
Entire Thread Thread List

Name: Anonymous 2017-07-24 16:31

/g/ is sad, not because the people are stupid, but because CS curricula are stupid and fill their heads with crap, which makes them look stupid when they repeat it. This is what they're teaching these days. Lisp and Haskell. Haskell and Lisp. Java. C++. C. Lisp and Haskell. C. C#. Lisp. Haskell. Idris. C. Lisp. Java. JavaScript. PHP. C. Lisp.

Name: VIPPER 2017-07-24 19:59

nice coded message

Name: Anonymous 2017-07-25 0:35

/g/ was never about programming.

Name: Anonymous 2017-07-25 1:05

not because the people are stupid
lol
Don't change these.
Name: Email:
Entire Thread Thread List

Name: Anonymous 2017-07-24 4:17

This came up in a /sci thread
(1-10 ->)
1,4,9,(1)6,(2)5,(3)6,(4)9,(6)4,(8)1,(10)0

How difficult is reverse mapping a square this way? (it runs least significant digit first lol)
The 5 newest replies are shown below.
Read this thread from the beginning.

Name: Anonymous 2017-07-24 11:51

>>2
It should map \(x\) to \(x^2\), ie perform an integer square root, but it only keeps the 1-10 lookup table, and has a two:one branch per digit

Name: Anonymous 2017-07-24 12:04

try a big ugly number test

x = sqrt(123456789)

start with 9, first digit of x is a 3 (+0) or a 7 (+4) {3*3's or 7*7's}
second digit 8 isn't in our map, but 8-4 = 4 is, giving a 2 (+0) or 8 (+6), and making first digit 7
third digit 7 again isn't in but 7-6 = is, giving a 1 or 9 (+8), and making second digit 8
..etc

Name: Anonymous 2017-07-24 14:10

>>3
it's bbcode

Name: Anonymous 2017-07-25 1:06

>>4
I still don't get it.

Name: Anonymous 2017-07-25 9:57

>>7
23*23 = 529
123*123 = 15129
2123*2123 = 4507129
42123*42123 = 1774347129
142123*142123 = 20198947129
5142123*5142123 = 26441428947129
75142123*75142123 = 5646338648947129
Don't change these.
Name: Email:
Entire Thread Thread List

Name: Anonymous 2017-06-28 6:16

Discuss.
The 5 newest replies are shown below.
Read this thread from the beginning.

Name: Anonymous 2017-07-22 18:26

Name: Anonymous 2017-07-23 13:10

>>137
Why bully hatate?

Name: VIPPER 2017-07-23 14:08

they shall all join my harem of programmers!

Name: Anonymous 2017-07-24 6:42

you shall all join my harem of dubs

Name: Anonymous 2017-07-24 6:57

The whole idea of a harem is ridiculous: Has anyone seen women at work?
stuck dozens of bitchy, sexually frustrated(you can't f them all 24/7) women in one place and expect them to live peacefully. Its an emotional minefield.
How do they prevent them killing/beating each other and/or killing the harem owner?
Sexbots will be far better/safer alternative if they existed.
Don't change these.
Name: Email:
Entire Thread Thread List

Name: george eroge jones 2017-06-28 18:35

made in s-exp instead of xml (because xml is fucking shit)?

Name: Anonymous 2017-06-28 20:45

Just use NNTP. It's much better than things like RSS.

Name: Anonymous 2017-06-29 5:53

((()()()))))()(((()))))))))(()())))))))((((((()())()))))(())()))

Name: Anonymous 2017-07-23 3:52

>>3
What did you just call me?

Name: Anonymous 2017-07-23 10:02

It would be good if your news is lisp executables i suppose
Don't change these.
Name: Email:
Entire Thread Thread List

Name: Anonymous 2017-07-20 16:52

Cudder is the type of person who would use ASN.1
The 5 newest replies are shown below.
Read this thread from the beginning.

Name: Cudder !cXCudderUE 2017-07-21 3:23

Yes?

Name: Anonymous 2017-07-22 23:33

IN BRAUNAU AUSTRIA BORN AND RAISED
VIENNA WAS WHERE I SPENT MOST OF MY DAYS
CHILLIN' OUT, MAXING, RELAXING ALL COOL
AND THINKING OF WAYS TO ANNIHILATE THE JEWS
WHEN A COUPLE OF KIKES
WHO WERE UP TO NO GOOD
STARTED RAISING LOANS IN MY NEIGHBORHOOD
I SET UP ONE LITTLE CAMP AND RUSSIA GOT SCARED
THEY SAID "IF YOU INVADE POLAND CAN WE AT LEAST SHARE?"
I WHISTLED FOR MY CAR AND WHEN IT CAME NEAR
(Post truncated)

Name: Anonymous 2017-07-23 5:28

>>4
Such beautiful European music.

Name: Anonymous 2017-07-23 20:42

>>4
Terrible

Name: Anonymous 2017-07-24 1:16

ok. so?
Don't change these.
Name: Email:
Entire Thread Thread List

Name: Anonymous 2017-07-22 1:12

1. Rule of Modularity: Write simple parts connected by pipes, sed, grep, and shell scripts.

2. Rule of Clarity: Clarity is better than cleverness.

3. Rule of Composition: Design programs to output text streams to other programs.

4. Rule of Separation: Separate policy from mechanism; separate interfaces from engines.

5. Rule of Simplicity: Design for simplicity; add error handling only where you must.

6. Rule of Parsimony: Write a big program only when it grew from a small program.

7. Rule of Transparency: Design for C programmers to make inspection and debugging easier.

8. Rule of Robustness: Robustness is the child of abort and stderr.

9. Rule of Representation: Fold knowledge into data so program logic can be stupid and robust.

10. Rule of Least Surprise: In interface design, always do the backwards compatible thing.

11. Rule of Silence: When a program has nothing surprising to say, it should say nothing.

12. Rule of Repair: When you must fail, abort and dump core.

13. Rule of Economy: Programmer time is expensive; conserve it in preference to machine time.

14. Rule of Generation: Avoid hand-hacking; write programs to write programs when you can.

15. Rule of Optimization: Prototype before polishing. Get it popular so you can get others to optimize it.

16. Rule of Diversity: Distrust all claims for “one true way” unless it's the Unix philosophy.

17. Rule of Extensibility: Design for the PDP-11, because the future will never come.
The 5 newest replies are shown below.
Read this thread from the beginning.

Name: Anonymous 2017-07-22 17:23

>>3
UNIX is the anti-FORTRAN. FORTRAN was a huge advancement in compiler technology and high-level programming. It led to new hardware features.

Allen: That’s right. Well, it was an unhappy class. But in the end, it was an amazing experience for all of us because Fortran was not only a language, but they had provided a compiler which was extremely advanced, and laid the foundations for the structure of compilers today.

...

Allen: Yes. And because the memory-latency problem was being solved by a lot of concurrency in the hardware—very complex concurrency. And the memory organization itself was multiway-interleaved and it was unpredictable what order data would be delivered to the computational unit. Six accesses could be in flight at the same time. There were pipelines in the computational unit itself and there was an ability for multiple instructions to be in execution at the same time. And the most complicated unit on the machine was a look-ahead unit, because they had precise interrupts as part of the architectural design, so not only did it have to keep track of all the concurrency going forward, but they had to back it out when there was an interrupt.

It was an extremely complicated machine and a wonderful one to program. The compiler had a very big challenge in order to take advantage of it. It was a wonderfully challenging project.

(Post truncated)

Name: Anonymous 2017-07-22 19:13

>But they still overspecify. The core thing is that it specifies location of data. If you look at these other languages, they stayed away from specifying the location of data and how to move it, where to put it in the machine. It was ultimately about its value at any point.
I don't get it, is he against static typing???
If not, type values are interchangeable to any degree with type punning:
C has very loose type conversion rules.

Name: Anonymous 2017-07-22 19:27

int a=-1;//specifying the location of data and how to move it
char* thirdbyteofa=((char*)(&a))+2;
float* floatvalueofa=(((float*)&a));
void* rawpointerofa=(void*)&a;

Name: Anonymous 2017-07-22 21:26

>>6
Also structure packing.

Name: Anonymous 2017-07-22 21:34

Un-Philosophical Thinking
Don't change these.
Name: Email:
Entire Thread Thread List

Name: Anonymous 2017-07-07 3:15

Paul Graham says languages he ``cavalierly dismissed'' before he ``even tried writing programs in'' ``have been bad'' and ``just smelled wrong'' because in his brain, they were ``designed for other people to use'', despite the creators of these languages being their biggest promoters. This is the mentality of a mental midget.

Historically, languages designed for other people to use have been bad: Cobol, PL/I, Pascal, Ada, C++. The good languages have been those that were designed for their own creators: C, Perl, Smalltalk, Lisp.

It may seem cavalier to dismiss a language before you've even tried writing programs in it. But this is something all programmers have to do. There are too many technologies out there to learn them all. You have to learn to judge by outward signs which will be worth your time. I have likewise cavalierly dismissed Cobol, Ada, Visual Basic, the IBM AS400, VRML, ISO 9000, the SET protocol, VMS, Novell Netware, and CORBA, among others. They just smelled wrong.
The 5 newest replies are shown below.
Read this thread from the beginning.

Name: Anonymous 2017-07-22 4:10

>>22
Why aren't you using netcat instead of browser automatically constructing packets for you?

Name: Anonymous 2017-07-22 16:48

>>23
Obviously because you can't always do that, and because it's not trivial.

Name: Anonymous 2017-07-22 18:25

Mental midget madness.

Mental midget middle managers fresh off the street who load me up with finicky end-user requests and wonder why I never get them done, resulting in them thinking I'm incompetent. Yet, they don't realize I've got a backlog of R&D tasks far too advanced for them to understand and the CTO is on an extended vacation for 2 months leaving me with no one to explain to them to fuck off.

Mental midget so-called "C++" programmers who are stuck in the C++98 days and give you a blank stare when you try to explain to them the finer points of pattern matching, multi-dispatch, algebraic types, concepts and the likes and how it can be done with sfinae/enable_if/decltype/deduction guides/etc. They then fuck up your code and take it in a completely opposite direction of what you had originally intended, shitting all over it with Java-esque OOPs turds, tons of sloppy whitespace and redundant gradeschool comments.

Example:

// dereference the value here and pass it to the lambda, duhhhhh
task(*value)

(Post truncated)

Name: Anonymous 2017-07-22 18:32

>>25
At least Lisp won't suffer when the bubble bursts this time. Then again, the first winter already did so much damage that there simply isn't much to ruin any more.

Name: Anonymous 2017-07-22 18:52

>>26
The AI Winter was divine retribution for pro-UNIX Lispers polluting the world's computers with C, UNIX and POSIX.

https://en.wikipedia.org/wiki/Richard_Stallman
Stallman started the project on his own and describes: "As an operating system developer, I had the right skills for this job. So even though I could not take success for granted, I realized that I was elected to do the job. I chose to make the system compatible with Unix so that it would be portable, and so that Unix users could easily switch to it."[33]

https://en.wikipedia.org/wiki/Leonard_H._Tower_Jr.
In 1986, Tower assisted Richard Stallman with Stallman's initial plan to base the C compiler for the GNU Project on a Pastel compiler Stallman had obtained from Lawrence Livermore Lab.[9] Tower worked on rewriting the existing code from Pastel, a variation of Pascal, into C[1] while Stallman worked on building the new C front end. Stallman dropped that plan when he discovered the Livermore compiler required too much memory, concluding, "I would have to write a new compiler from scratch. That new compiler is now known as GCC; none of the Pastel compiler is used in it, but I managed to adapt and use the C front end that I had written."[9] Stallman released his new GNU C compiler March 22, 1987,[10] acknowledging others' contributions, including Tower's, who "wrote parts of the parser, RTL generator, RTL definitions, and of the Vax machine description" based on ideas contributed by Jack Davidson and Christopher Fraser.[2][11]
Don't change these.
Name: Email:
Entire Thread Thread List
New thread
Don't change these.
Subject:
Name: Email: