I went down this road with their Japanese.. in summary, their focussing on "words" vs "phrasing/talking" from day one like Pimsleur was, wat killed it for me.
On that note Pimsleur was/is EXCELLENT for me:
1. Focusing on phrases vs words
2. Talking from Day 1
3. Lesson oriented.
Pimsleur is the best thing I've found for my first ~30 hours of learning a language (Courses 1 and 2, basically). It gets to the (IMO) most important words/phrases/interactions first, and the spaced repetition works well for me. It almost feels like magic is happening in my brain. In find going past 1 and 2 is still worth my time, but I usually start to sense diminishing returns, and at that point I start to look around for other options to supplement it.
Pimsleur's implicit way of teaching grammar works well for me for the most basic stuff, but as it gets into more nuanced grammar, it gets a bit less helpful for me. It also feels less magical to me once it gets past the first couple hundred words.
I'm waiting for the excellent F# Article about railroad-coding to be posted here.
Required F#e reading :) No not trolling. Am on mobile and traveling else I would have searched-posted
I went the rabbit hole of exploring SVG "decimal precision-related" glitches in browser implementations and to my grief I must confirm that there really are blatant cross-browser issues. It's fact that my tests went a bit over-the-top with dimensions -- who would make 1e9 or 1e-9 wide viewBox in real world anyway? -- but since refraining from doing so is not discouraged in the specs, one would expect it would scale (pun intended) at least few orders of magnitude. The results for my particular testcase showed that "safe" range was only between 2e3 and 2e5: [1].
> who would make 1e9 or 1e-9 wide viewBox in real world anyway?
Back in about 2008 I made an SVG diagram showing the height of various satellite orbits above earth, specifying the SVG at 1:1 scale - making the image 84,000 km wide.
Sadly a load of file viewers choked on it, so I had to settle for a downscaled version. It seems the 'scalable' in 'scalable vector graphics' only goes so far.
Ha, nice! I secretly hoped someone would mention their real-world usage of "ridiculously" large SVG dimensions, so thanks for the reference!
Your story implies there actually were some viewers that could handle it correctly? Could you recall more details what were they? (My testing was pitifully limited to current browsers only, but I know there must be vast amount of other viewers.)
And if I may ask, did you map one SVG "point" to some length unit (e.g. meter, so getting 84e6 wide wiewBox), or did you assume 90 DPI "pixel" mapping to ~0.2822 mm?
However the browsers don't crash or run out of memory, so they've got that going for them. And if you embed the image in a web page with <img src='84km.svg' width=1000 height=1000> chromium almost manages to display it.
SVG lets you specify sizes in a bunch of different units, but there's actually a fixed ratio between them - in SVG, 1mm means is 3.78px regardless of your display or printer's DPI.
So I didn't scale mm to SVG's arbitrary length units - but the standard did.
So at this point we don't know about any viewer capable of handling Earths orbit sized SVG? That's sad.
> However the browsers don't crash or run out of memory
Good news for your sample. Yet in some browsers there prevail some open issues, just the limits are now farther. For example feeding this SVG to my Firefox almost instantly exhausts my RAM and makes the browser window unusable for a while:
I tried to make a daily timeline in SVG where 1 unit = 1 second. There are 86400 seconds in a day. Both Firefox and Chrome did not render the image properly, so I had to scale the numbers down too. What a shame.
Also, browsers seem to render svg circular arcs using bezier curves. At high zoom levels there can be quite a discrepancy between the actual curve (drawn using lots of straight line segments, say) and what the browser renders for a circle.
Do they? I thought this is more issue on the source code side, rather than implementation: this is actually my pet-peeves, that most SVG *authoring tools* never output circular arcs and always use cubic béziers approximations instead. So we nearly ever see real circles or their segments, even though authors use them in their designs all the time.
It was a few years ago and I'm unable to reproduce it. Circles and circle approximations from straight lines seem to coincide exactly in Firefox and Edge now.
I was generating diagrams using my own code so I'm positive they were circular arcs. Tangents weren't tangent and it took me a while to realise that the problem was the browser rendering something that wasn't quite a circle. I assumed it was a bezier approximation but I didn't verify that. Whatever it was it seems to be fixed.
Another thing I've noticed is that Chrome doesn't seem to render SVGs with anti aliasing (at least not always?). This makes SVGs unsuitable for lots of kiosk-style systems, where you often have Chrome showing a web page on a relatively large low resolution screen.
1. Icon-Button-Click-Area: Click on the STAR (Panel Type) I can only activate it via putting the mouse cursor at the left bottom of icon/button. Putting my cursor RIGHT on top in the middle does not activate it.
2. Panel-Split: Not sure if its related to 1, but I could only ever managed to figure out how to split my left horizontally plane once. Trying to split the right panel also like this, proved to be impossible (for me)
3. Sluggish-Feel: This could def be related to 1, but there seems to be a general delay between action(if it fires) and visual feedback
Suggestions:
* Re-look at GUI and make it more predictable/familiar in terms of interaction
(click-area, feedback,speed)
* Templates-For-Tab: Would be nice when creating a new tab, I could pre-select from a few templates, silly examples follows:
- 4 box splits),
- 2 vertical splits,
- 3-splits (image, code, text)
b) GUI-Feedback: Just to make it feel more responsive.
c) Use-Cases: I do like the free-form-thinking with wide constraints ntoe taking idea. I can even see it being used for: WebToon-Layouts, Storyboards, User-Testing, Use-Cases etc.
Again Congrats On Launching ! It's 90% of the challenge !
Thank you! yeah launching was a hard step!
Thanks for the GUI feedback, Ill take a look at it, user testing did not report that particular issue (or for me in chrome) but I will definitely test it with different browser settings (Thanks for the edit, Ill check that). Layout issues, yeah, Plus button will open the bottom panel, and you can close it with the Minus button on that bottom panel. That's all like 2 main, 2 expandable on the bottom!
Awesome, template idea is really great.
Yeah sluggishness is notable, ill need to fix it!
Apologize for the bad experience, But appreciate all the inputs! Thanks!
On that note Pimsleur was/is EXCELLENT for me: 1. Focusing on phrases vs words 2. Talking from Day 1 3. Lesson oriented.