Tobu

module-local as in, creating a new type that can't be exchanged with the outside? Or converting the value's type on the fly when it gets passed somewhere else? I doubt either would be very usable.

Edit: the page refers to open classes, and I think the idea is that you can redefine methods on Object and have it apply to every object.

Nope. In is_subtype:

> # If `sub` is a formal type, then it is accepted if its bound is accepted https://github.com/privat/nit/blob/2323b17d46c873e8c6c41b75d...

Ruby is dynamic and the interpreter is feature-rich. People are just exercising self-discipline. Nit intends to be “a robust statically typed programming language” which is very different.

Also, could you point me to the Nim feature? All I see is overloading.

Python has re.escape; awk can take variable definitions from the command line:

  echo b |awk '/b/{print a}' a=4

vim's regex syntax is unusual and sucky. Thankfully running commands is super-easy:

:%!sed …

Are you sure? sed has -z, it's useful.

Could have to do with charset handling.

For the really complex stuff, there's rejit[0]. I wonder if LuaJIT would work; these tools also need IO tricks to be fast.

[0] https://lwn.net/Articles/589009/

> I used the default OS X versions of these tools. The versions were Perl 5.16.2, Awk 20070501, and some version of BSD sed from 2005

http://nitlanguage.org/manual/genericity/

> Unlike many object-oriented languages, generic classes in Nit yield a kind of sub-typing. For example, Pair[Int] is a subtype of Pair[Object].

Sounds completely broken. What if Pair[E] is contravariant on E?

  class Pair[E]
      fun contains(E): Bool
      fun clamp(E): Bool
  end

> http://nitlanguage.org/refinement/ (redefining any method)

That's spooky action at a distance. It breaks modularity, could cause packaging hell.

CHANGES: https://github.com/openssl/openssl/compare/OpenSSL_1_0_1j......

Indeed, just about every brand of SSL load balancer was doing it wrong:

https://www.imperialviolet.org/2014/12/08/poodleagain.html

Longer keys could also make some compromises less obvious; finding identical keys -> bad entropy, weak keys (Debian/OpenSSL, lots of devices). I don't know if anyone found backdoored key generators that aren't based on weak entropy.

OpenID Connect is based on OAuth.

Name-checking terrorists is so thin it's transparent.

Also, the SourceForge link was for pastebin source code[0] and not an actual pastebin.

IMHO it was a lazy request from the copyright lobby, which is seeking to criminalize anonymous text and links. They don't care that it's insane, the world isn't changed by being reasonable; at worst they'd have shifted the Overton window and made the other wing of the lobby look sane. The politicians barely care, and another level of jaded drones didn't bother to contact anybody[1], put up a DNS block and went home.

[0] https://news.ycombinator.com/item?id=8820591

[1] https://news.ycombinator.com/item?id=8820289

Distro packagers generate a listing of public symbols (tagging a symbol with the version number when it is introduced) to catch incompatibilities. It's like static typing, it takes a bit of getting used to but it's very reliable.

https://www.debian.org/doc/manuals/maint-guide/advanced.en.h...

Maybe this doesn't work for the library ecosystem (standard libraries being where modules go to die), but the language and VM specs are very well designed.

They could always have their own fork/branch for upcoming releases of Ruby. It's not like the spec has to freeze the language.

Nanobots are decades away and may stay that way, but nanotubes are mass-produced and pollution is a problem. The thin fiber is like asbestos except more volatile, and it can cause cancer. http://www.particleandfibretoxicology.com/content/11/1/59

With PyPy: - `is` is very slightly faster - '%d' is slightly faster

Yet another caveat: the differences are often less that 1%, statistically not significant.

Those are the quirks of CPython 2.7. The best optimisation is to run with PyPy — those benchmarks run about 10 times faster.

After that, if you want to optimise, you need an applicative benchmark. A microbenchmark won't work because type specialisation runs for (traces of) the program as a whole.

It's standard, Linux distributions generally install NetworkManager. The tweaks are for people who want more control or have less typical setups.

Dated. DHCP can be done in milliseconds, 50ms over a WiFi connection:

https://plus.google.com/+TomGundersen/posts/eztZWbwmxM8

It's been upstreamed, hasn't it?

Announcement http://www.passmark.com/forum/showthread.php?4836-MemTest86-...

Previous discussion https://news.ycombinator.com/item?id=8713411

Rust needs LLVM for code generation. Realistically they could only trust an interpreted language like (non-jit) Lua.

Or they could adopt ZeroVM/NaCl, which would shift the balance towards compiled languages again.

Stripping the binaries with filter-branch, or normalising them using smudge filters (for example, making sure zip-based formats use no compression).

me.ga or mediafire would work.

Since working memory is so important, will there be any policy to get children to practice that while they have the extra mental plasticity? Learning languages takes skill, effort and dedication, focusing on the skills part early would give a good return on the teaching investment.

Critical sentiments can be useful when they are of the form: “X didn't work, we moved to Y because blah blah and we did it by yada yada”.

Whenever something needs fixing in TLS we always hear about the OpenSSL patch first, so it seems like the project is healthy. I think this (and some of the context around the Debian incident) points out that we should be looking at replacements focused on implementation safety (bluishcoder's ATS-based demonstration looks like the right direction), good defaults, and a simpler API (one that also doesn't give so much leeway to shoot oneself in the foot through configurability).

Just to clarify, aside from the footnotes this is a translation of the original page.

There's another hterm, an xterm implemented in js and shipped with Chromium OS:

- https://chromium.googlesource.com/apps/libapps/+/master/hter...

- https://chromium.googlesource.com/apps/libapps/+/master/nass...

- https://groups.google.com/a/chromium.org/d/forum/chromium-ht...

I think Linus has been pretty clear on both topics (fix A, and if you won't, fix B) and on general policy (don't break it for users or I don't want to work with you in the kernel). Yeah, the reporter could have framed it better from the start, but the developers are supposed to be adults and handle imperfect bug reports too.

FWIW, I don't really consider the first issue fixed. The trigger was lost in a refactoring that can't be backported, and there are probably other ways to trigger the issue.