i4k

The "status quo" in the dark ages was: bigotry, fanaticism, supremacism, conspiratorial theories, anti-science, slavery, and so on. At this time, writing anything against the masses beliefs would lead to persecution and death. People died trying to educate others and at the same time others extremist ideas were born but the society learned to ignore them. The good ideas were victorious.

Remember: On May 10, 1933 around 25,000 books from 34 university towns in Germany were burned! Some of those books were unique, their ideas will never be known by society.

If you go back in time, 50 years, 100 years, 1000 years back, whatever, the society always approved horrendous ideas and few people fought back. You should never trust the "status quo" or the "justice warriors" of the internet, as they could easily be on the wrong side of history. The access to information is the solution not the problem.

In my opinion, asking for censorship shows no respect for the ones that died trying to change the world.

You are trying to build Go in a way it wasn't designed for.

Go encourages absolute import paths (relative to $GOPATH) and solves a myriad of other language faults in this way. A good benefit is go-gettable projects, where all dependencies can be reached without a setup/configuration file (like setup.py, requirements.txt, and so on).

If you do not try to use Go like other language, your build should be something like:

  $ GOPATH=$PWD/some/path go get github.com/foo/bar

Thanks for the help!

https://groups.google.com/forum/#!msg/comp.lang.forth/XCtQPZ...

Doing software this way makes bash and emacs working well, but hard to make other softwares interact with both of them... Sublime, acme, micro, and so on can benefit of a better solution. In the same way, other shell should work fine inside emacs (M-x ansi-term).

But software design is not expected here (see downvotes)

hahaha

Next release it will check the variables $INSIDE_ACME, $INSIDE_SUBLIME and $INSIDE_NOTEPADPLUSPLUS

After four releases versions bash starts to get regular syntax?

  https://github.com/j-bennet/wharfee
  https://github.com/j-bennet/wharfee/issues/89

112.567 repositories with docker in name.

Big companies/projects are using docker.* repo names. To cite some:

  spotify/docker-gc
  couchbase/docker
  citusdata/docker
  nodejs/docker-node

And think, Go was created with intent for faster builds. My bigger go project builds faster than `docker run` starts up...

The author forget to say that this way docker will setup a network namespaces, bridge, mount a unionfs (overlayfs, aufs, etc), lots of other things, make a chroot and then finally execute the go tool...

And Go doesn't even need to be installed on the OS, it can be placed anywhere, you only need to set the GOROOT env var. (For bash-users, the gvm script automate the build/download of every go version you want in your $HOME)

The only point of the article is when you're not a Go programmer and want to test some Go project...

Spender talks about it for a long time: https://grsecurity.net/~spender/interview_notes.txt

Linux developers fix security bugs in irresponsible ways, saying nothing about the attack vector or CVE's involved. Sometimes multiple vulnerabilities are addressed in the same patch, making hard to track the fix.

For more information see the exploit below: https://grsecurity.net/~spender/exploits/64bit_dos.c

The list of kernel vulnerabilities involving namespaces is bigger each day, as the paper shows, but the industry still uses "container" and "security" in the same quotes.

How persistent data will be managed isn't detailed in the document.

Seccomp-bfp is a good enhancement. It can really fix the well know security issue of docker when using volumes with write permissions.

Still wondering what's the plan for persistent data. If someone has more info, please share :)

Some questions:

  - Do they provide their own implementation of containers or
    rely on some already existing (docker, rkt, etc)?
  - How containers communicate? what protocol?
  - How filesystem is handled? Containers have volumes for file system sharing?
  - What's the plan for devices management? How my USB
    pendrive, speaker or webcam is available inside a 
    container?

Thanks for Myrddin! It's a very promising language! Well designed and using the right tools.

People of #cat-v showed it to me and since then I look forward to play with it!

Yes, plumber is the app behind the scenes that make acme so much integrated with OS and other apps. The same applies for right-click on the text between '<' and '>' in includes (in C source files) for opening header files. That's the kind of programming environment that I miss when using emacs/vi.

The same (or very close) interface was available for unix in 1982 with the Blit graphics terminal. Blit was created by Rob Pike (acme creator) too and it influenced the next Pike's GUIs (rio and 8½).

In Plan9's rio, windows are treated as completely editable text, then the mouse chords for cut-and-paste works for all applications transparently.

Blit promotional video: https://www.youtube.com/watch?v=emh22gT5e9k

Wiki: https://en.wikipedia.org/wiki/Blit_(computer_terminal)

For terminal, acme have support for windows attached to programs (if the program is a shell, you have something like a terminal). From the manpage:

    Win creates a new acme window and runs a command (default /bin/rc) in it, 
    turning the window into something analogous to an rio(1) window.
    Executing text in a win window with button 2 is similar to using Send.

Some other applications of plan9 have taken the advantage of acme UI (like abaco web browser) but they aren't builtin inside acme.

But I agree that it's not the best choice for some languages or environments.

In my current view, the lack of syntax highlighting is a great feature!

For now emacs is only for lisp/scheme languages.