HN user

DZittersteyn

21 karma
Posts0
Comments21
View on HN
No posts found.

Looks like they did a bit of premature rounding:

the difference between 38℃ and 94℃ is 100.8Δ℉ rather than the 100Δ℉ that was probably there in the original markings. It's the closest you can come to the correct values though, 93℃ is off by 1Δ℉

They then assumed 100Δ℉ = 56Δ℃, and applied that to the rest of the dial.

That means the values on the dial are off a bit, and should be: 38, 93, 149, 204, 260, 316, 371, 427

It makes sense to me that the weekend comes at the end of the week, but then again, I don't know what came first, the term "weekend" or the convention of Sunday being the start of the week in some countries

I also used to have this impression, I think I got this from Rails and Django docs, maybe you read something similar?

Rails comes with built-in support for SQLite, which is a lightweight serverless database application. While a busy production environment may overload SQLite, it works well for development and testing. Rails defaults to using a SQLite database when creating a new project, but you can always change it later.

By default, the configuration uses SQLite. If you’re new to databases, or you’re just interested in trying Django, this is the easiest choice. SQLite is included in Python, so you won’t need to install anything else to support your database. When starting your first real project, however, you may want to use a more scalable database like PostgreSQL, to avoid database-switching headaches down the road.

Is there a reason to be doing doing a closing, and then a sequence of erosions, followed by dilations?

Since closing(image, str.elem.) == erode(dilate(image, str.elem), str.elem), it feels like you could better use an erosion (remove noise) followed by a closing (to fill up the empty spaces) instead of the other way around?

This is answering the question: "Does tihs email address exist?", which is nice, but usually not the question being asked. The more common question is "Is this the email address of the user", which can only be answered by a confirmation email.

You could use this method as a first-line validation though, to give the user some feedback (similar to not implementing the full RFC regex, but simply checking /.+@.+\..+/)

A lot of the arguments against Java seem to focus on "Time-to-Hello-World". While I agree that the first time you execute a program and see those magic words appear on your terminal, I don't think we should judge a language on that. Visual basic has a very short TTHW (esp. if you take into account the time spent on learning about terminal emulators for most languages), that doesn't make it a good language.

If you take an OO programming language as your teaching language, you need to introduce a number of concepts first.

Hr 1: Talk about classes and objects. Introduce the Car and Bike object, that both have the method 'steer()', the attribute 'wheels' and only the car has the property 'hood'. Introduce return types here, as well as arrays.

Hr 2: Then explain how the 'color' on Car is public, while you'd like the accelerate() method to be private.

Hr 3: Explain how some methods and attributes are static. what is a property of the concept 'Car' and what is an attribute of an instance?

In Hr 4 you introduce them to the classes String and System.

Your students will now know:

-class -public -static -void -String[]

You can now tell them about the 'magic' that makes things start, the 'main' method.

Class MyFirstProgram { public static void main(String[] args) { System.out.println("Hello World"); } }

No magic, and a nice start to becoming a proper OO-programmer.

If you want too teach them FP, Haskell is not a bad way to go. If you want to teach them OO, Java isn't as crappy as people say it is.

Oh man please no. Imagine having this in your pocket and playing music! The little amount of stress your pocket puts on it will make your music jump.

Imagine having a magsafe connector on a laptop without a battery. So every time your connector gets a bump your laptop shuts down. The reason magsafe works is because you don't need constant power, so a short interruption is okay.

Wow, this is really irresponsible behavior, I would've expected something better from Mozilla.. Until now they've first offered an alternative (e.g. pdf.js) before trying to move away from a tech.

Marking a current version as unsafe, even when there are no known exploits is simply ridiculous. I'd love to see the reaction of Mozilla if Microsoft decided to mark all Firefox releases as unsafe, and give a big security warning whenever you installed FF.

Especially if the UI for unblocking it in FF is as obtuse as the discussion implies..

Might it be that the Win7/Vista drivers for the MBA are worse that the OSX drivers?

We see the comparisons: Surface <-> iPad, OSX MBA <-> Win7/Vista MBA

Surface has different architecture than the iPad, so the battery difference is easily explained, and maybe driver support is just less than stellar, meaning HW isn't as efficient and/or doesn't scale back quickly enough?

I had an Asus laptop some years ago that would last 3 hours under Vista, and would be dead in the water in 1 hour under Ubuntu. I think it was either GPU or CPU scaling or both that wasn't supported in the linux drivers I was using