matdes
You are correct that you should be writing your actual angular code in those separate files. And doesn't it make sense that the export of a controller file is an injectable controller? None of this "dependency injection via a string which gets turned into a reference to real code later"
:: means "the stuff after this is the type signature"
Normally, a type signature can be as simple as something like
'x' :: Char
which is the type signature of the character 'x'. Looking at the type signature of 12 shows two parts "Num a =>" and "a". This can be read as "it returns a generic type `a` that must be an instance of the type class Num", which sounds really complicated but isn't.
The "Num a =>" is a type class constraint on the returned type "a". Type classes are basically like interfaces, they set up constraints and methods that need to be implemented for that type, analogous to how in other languages a class can implement an interface. For example, the Eq type class mandates you define the (==) and (/=) methods for that type, analogous to how something like the interface Comparable in Java requires you to define the compareTo method.
Thus the concrete type "Integer" is an instance of type class "Eq" because it implements those (==) and (/=)
Num is an example of a type class, just like Eq. But Num requires you to define a few more methods
class Num a where
(+) :: a -> a -> a
(*) :: a -> a -> a
(-) :: a -> a -> a
negate :: a -> a
abs :: a -> a
signum :: a -> a
fromInteger :: Integer -> a
So all of the things you think of as "numbers" are all types that implement "Num", e.g. an Integer, a Float, a Double.So going back, "12 :: Num a => a" means 12 can be any type which implements Num, which is really just a fancy way of saying "this number can be cast into any numeric type". You can perform this casting manually!
λ (5 + 7) :: Integer
12:: Integer
λ (5 + 7) :: Float
12.0:: Floatyes?
> So what does it mean to write functional tests? I'd argue that writing modular React components is a form of functional testing. Devcards[1] is similar, and looks to me exactly like what would be considered functional testing. These two workflows feel much more natural than testing UIs methods like automated selenium browser interactions to generate screenshots.
no.
Significant overhead costs to go from nothing to steady-state instantaneously would be enough to scare me.
Model is a well-defined term in the domain-driven design world, as in "Domain Model"
Lotus was never a ruby web application framework. Guess Apple's going to have to change the name of Swift because of that other programming language, amirite?
c.f. "You are hurting your cause by being angry"
try to be less of a trope.
embrace OO
umm...I've got something to tell you...
You're telling me, with no question, if you were to see this woman in the middle of the street, you would think she could absolutely be a coder?
You're telling me if you saw her at a conference, you would think she was there as an expert, and not to find a husband, or was part of the booth babes or help staff?
You're telling me if you saw her on the roster to speak at a conference, you'd think she got it because of her prowess and intellect, and not because she dolled up?
No. And if you actually go to the link to the original question, you'll see that cat doesn't exist.
Last, I would disagree that `cat file` is equivalent to `select * from table`, his argument makes the comparison that `cat file` is equivalent to `table` itself, or `load data into table` which needs to happen before any relation can be performed against it.
"Thanks for reporting the issue of plain text passwords to us. It's how passwords are handled with the membership software we use for Tuts+ Premium, which isn't extremely well coded and something we want to rebuild from scratch. In the mean-time our dev team will be hacking the software to bring password security up to the best practices we advocate on our Tuts+ sites, like Nettuts+."
Not only was this issue brought up to them, they stated very clearly that they were working to bring their password security up to best practices. In a YEAR, they couldn't hack on a password hash or rebuild their plugin from scratch?
If anyone knows if there is a lawsuit pending that could use my email as evidence, please let me know.