HN user

bmichel

224 karma

http://blog.menfin.info

Posts24
Comments19
View on HN
hcompany.ai 3mo ago

Holo3: Breaking the Computer Use Frontier

bmichel
1pts0
palant.info 4y ago

How did LastPass master passwords get compromised?

bmichel
309pts184
forum.cozy.io 9y ago

Request for comments about the next Cozy architecture

bmichel
3pts1
www.infoq.com 10y ago

Designing with passion

bmichel
1pts0
blog.cozycloud.cc 10y ago

Cozy desktop client for Linux is coming

bmichel
4pts0
blog.bamlab.fr 11y ago

How to build an offline map system for an hybrid app?

bmichel
1pts0
medium.com 11y ago

Generation Y in office; part 2

bmichel
1pts0
medium.com 11y ago

How do I get addicted to Generation Y?

bmichel
1pts1
medium.com 11y ago

Generation Y in the office. part 1

bmichel
2pts0
github.com 11y ago

Face'n'feature detection

bmichel
1pts0
dev.af83.com 12y ago

How to document your Grape API using Swagger UI

bmichel
1pts0
dev.af83.com 12y ago

A journey in golang package manager

bmichel
2pts1
dev.af83.com 12y ago

Parsing API responses in Go

bmichel
3pts0
dev.af83.com 12y ago

Record post params with nginx, redis & lua

bmichel
1pts0
dev.af83.com 13y ago

Learn about Elixir, notes from ElixirKaigi

bmichel
1pts0
dev.af83.com 13y ago

Why you should consider Beanstalkd

bmichel
1pts0
dev.af83.com 13y ago

Load testing web apps with Siege

bmichel
2pts0
github.com 13y ago

Show HN: Koalab, an html5 board

bmichel
1pts0
dev.af83.com 13y ago

Document-oriented database and migration

bmichel
3pts0
dev.af83.com 13y ago

Should we namespace Redis?

bmichel
1pts0
linuxfr.org 14y ago

Interview with Andrew Tanenbaum

bmichel
14pts1
linuxfr.org 15y ago

Interview of Lennart Poettering (avahi, systemd, pulseaudio and more)

bmichel
1pts0
dev.af83.com 16y ago

Acceptance tests on a PHP project with the cucumber / webrat / selenium trio

bmichel
1pts0
shakacss.af83.com 16y ago

ShakaCSS debug, a tiny bookmarklet for debugging CSS

bmichel
3pts0

CouchDB 4 may change a few things in this space. It will be based on top of FoundationDB, which should make it a lot better for running "at scale PaaS".

Featherweight Go 6 years ago

The former proposal was made by 2 members of the Go core team. And they are also in the team of the latter proposal. So, no, the first proposal wasn't good enough for the Go authors and the new proposal is in no way a guerilla attempt.

Thanks for the answers, I appreciate that.

If you have time, I have another round of questions:

1. Did you try formal methods like TLA+ on the client? I think that the logic covered by CanopyCheck may be a nice target.

2. Do you have some tests with several clients running at the same time on a shared directory? In particular, I think of the termination invariant where the clients are fighting because several users have reorganized the directory by moving a lot of stuff, and each client is trying to converge in a different direction (ie they are making operations that cancelled the ones made by other clients).

3. The article says "In the Nucleus data model, nodes are represented by a unique identifier". Does it happen that a node has to change its identifier? For example, in a scenario like this one:

      (ada) $ offline
    (grace) $ offline
    (grace) $ mv ~/Dropbox/shared/TODO.txt ~/Dropbox/private-grace/
      (ada) $ mv ~/Dropbox/shared/TODO.txt ~/Dropbox/private-ada/
      (ada) $ echo 'foo' >> ~/Dropbox/private-ada/TODO.txt
    (grace) $ echo 'bar' >> ~/Dropbox/private-grace/TODO.txt
      (ada) $ online
    (grace) $ online

Thanks for sharing your experience on this rewrite. I have a few questions:

1. I'm a bit surprised that you don't persist the scenarios of the tests after a failure, only its seed. Does it mean that when you want to replay it, you have to redo the minimization phase? Or, do you have a way to find a seed for the minimized scenario?

2. Do you have some tests where you generate a set of operations and play them twice: one time with the mocks and one time on the real servers to check that they have the same results?

3. The article says "Note also the importance of the commit hash, as another type of “test input” alongside the seed: if the code changes, the course of execution may change too!". How are you ensuring that a commit really fixes a bug, and not just change the execution path to a happy path where the conditions of the bug are not met? By playing again a lot of tests, or do you write a new unit test that exhibit the bug to ensure the reproductability?

4. Do you think we can say that CanopyCheck is applying randomized testing at the unit tests level and Trinity is applying it at the integration tests level?

Tanspiling from ES2015 to ES5 is no longer the main usage of babel. For example, there is transforming JSX to normal JS. And object rest/spread proprerties (ES2018) is often used by front developers, even if it is not supported by Edge. So, I don't think that babel and swc will be obsolete in 2 years. The most used transform plugins for those will change, but the parser and engine will remain. And having fast and robust tool here is a good thing for this field.

But how do you do your binary search on a set without enumerating/sorting it? For example, if at one step, you know that 28.3 is too small and 42 is too big, how do pick the number between them that will split your set in two?

Maybe it's just me, but I'm scared by this sentence from the Google ToS:

"When you upload or otherwise submit content to our Services, you give Google (and those we work with) a worldwide license to use, host, store, reproduce, modify, create derivative works (such as those resulting from translations, adaptations or other changes we make so that your content works better with our Services), communicate, publish, publicly perform, publicly display and distribute such content." -- http://www.google.com/intl/en/policies/terms/