798 karma · joined April 17, 2012
I can be contacted at my gmail: thomas.shadwell
What implementation of compile-to-javascript Go is this? They should add tags for closure compiler optimization, just simple optimisations (without type annotations, which are present, usefully in go) cuts the filesize by half.
Link:<[filename]>;rel=stylesheet
It's fun to use:
Link:<.>;rel=stylesheet
and detect the Accept: text/css header to serve a css file conditionally, too.
http://www.synthace.com/investors/
Amusingly, the link for their main sponsor's website goes to: "file:///C:/Users/sward/Downloads/www.sofinnova.fr"
He captured a cross-site request forgery token which was valid for all users.
logoutUrl: 'https://foobar.withgoogle.com/_ah/logout?continue=https://ww...
Correction: this seems to rely almost entirely on the content-type sniffing of the client-side, provided the content-disposition is 'attachment'.
- Heavy use of Javascript for what CSS is designed for: https://github.com/t4t5/sweetalert/blob/master/lib/sweet-ale...
- Inconsistent between function spacing followed by mixed tabs and spaces
- Odd use of DOM based attributes to pass configuration options
- Colourspace manipulation on each call where SASS would be effective https://github.com/t4t5/sweetalert/blob/master/lib/sweet-ale...
- Includes jquery, but uses it very little, instead opting to re-invent the wheel in most cases.
- Strange click event firing, gratuitous use of magic key code numbers https://github.com/t4t5/sweetalert/blob/master/lib/sweet-ale...
etc...
Edit: there is https://golden-layout.com/?gl-window=%7B%22g%22%3A%5B%7B%22o...
Please don't chastise me for disclosure ethics, this one was low-hanging fruit.
Here is one I wrote long enough ago for me to be divorced from its implementation flaws: https://github.com/TShadwell/go-shorten/blob/master/shorten/...
There is a Wikipedia article on this which may provide some wider information.
s, i := make([]T, 0, 6), 0
s = append(s, 1, 2, 3)
//[1 2 3]
fmt.Println(s[i:])
i += 3
s = append(s, 4, 5, 6)
//[4 5 6]
fmt.Println(s[i:])
i += 3 // [etc...]
//[1 2 3 4 5 6]
fmt.Println(s[:])
You can easily make references to each chunk of the slice you append without much difficulty or any re-sizing (the first s[:] will remain a slice of the first 3 items).
If you look at Lego vehicles for example, they all have to have disproportionately wide wheels to be able to navigate the studs on the bricks without getting caught.
In addition, there are the problems of forming non-rectangular and non 90 degree walls anywhere in the house, the problem of recognising and targeting the bricks correctly with the robot, the 'spray on' cement that seems a fantasy.