That kind of thinking results in an inevitable chicken and egg problem.
How did society get this way if it's all a construct? A secret cabal decided what constitutes a "masculine" activity and what constitutes a "feminine" activity, some indeterminate amount of time ago?
If I only like playing with toy cars because my father liked playing with toy cars, and my father only liked playing with toy cars because his father liked it, who was the first father and why did it stick?
The reality is that men and women have different biological compositions with different hormones and different instincts that organically give rise to different behaviors. Sure, toys are toys, and generally any kid will probably be happy with any toy, regardless of gender. But the idea that preferences in childhood development didn't arise organically is honestly not founded in reality.
No, you can't.
Because girls need a safe space to be girls (without any boys around) a lot more than boys need any more spaces where they can be boys without any girls around (there's enough of those).
> No, you can't. Because girls need a safe space to be girls (without any boys around) a lot more than boys need any more spaces where they can be boys without any girls around.
Its really important to consider who the class is for when looking at how you enjoyed it.
You took the class already having 'lots of prior programming experience'. This class was clearly designed for people who have never programmed in their life. This class was not designed for you.
I was in the very same situation when being taught the basic programming concepts in Python at University, after having held software dev jobs and written assembly and C for several years.
Scratch, Alice and others are great starting tools for kids around 5 to 13 who have never programmed before.
They're reasonable initial platforms to spend a couple of hours on for older people too (your age group and even upwards).
It might be worth talking to some of your peers who had never programmed and asking what they thought.
Its super easy to forget than only a little while ago, you also knew nothing.
I do agree that the whole course should not have been modelled around Alice. At your age you could probably pick up the Python REPL quickly after an initial into to the concepts in Alice.
I see no problem in encouraging contributions and donations in your CONTRIBUTING.md (that shows when creating an issue).
Especially in a large project.
But requiring a donation or code would mean that lots of bugs would go un-reported. Issues are just as much of a contribution to a project as code is.
Founders getting overwhelmed is solved by adding maintainers or transferring maintainership. Popular projects will be forked if the maintainer burns out and leaves.
Yes. Running a GPU at 100% continuously will significantly shorten the lifespan of the chip, the chances of picking up something that's not got much life left is high.
I'm really excited about ARM laptops, but only if:
* They have laptop-class performance, not tablet class performance
* They can have more than 4GB of RAM
* You can put reasonable sized standard SATA SSDs in them, or user-replaceable M.2 drives.
* You can easily wipe Windows off them and put Linux on it.
> You can easily wipe Windows off them and put Linux on it.
None of the modems are going to be supported in Linux because they all use blob drivers and are wholly proprietary.
ARM has no bios or standard boot procedure. Google requires coreboot on Chromebooks, for example, which allows Linux to run on the ARM targets. It is unlikely ARM laptops without Google's strong arm are going to support coreboot.
Qualcomm specifically leaves significant portions of the support code for their SoCs in binary blobs, unable to be used in generic kernels. There is no Linux kernel level support for almost any Qualcomm SoC, and even then they are often some of the better ones. The other "real" options are third parties with ARM's own CPUs on them, which would have ARM's GPUs which have no real device support in Linux (Lima is dead) compared to Qualcomm parts (Freedreno sees updates). Nvidias chips are probably the closest to usable, and Samsung's Exynos are completely unusable and mega-proprietary (you will have a hard time finding even custom Android ROMs for Samsung SoCs).
The ARM ecosystem as a whole is really, really toxic. It is all NIH'd out the butt, there are no standards, everything is proprietary, and nobody contributes upstream. By comparison, x86 is an angelic fantasy.
Why wouldn't they have more than 4 GB of RAM? Current Android flagships are shipping with 6 GB of RAM, and 8 GB phones have been announced.
I'm not sure about the laptop-class performance requirement, you mean for light browsing and office tasks, they should be there already (even with the emulation penalty).
Lots of Chromebooks don't come with more than 4GB of RAM, theres no reason why they couldn't have more too. But the mostly don't because the target market is not seen as needing it.
I've spoken quite a few times and several different conferences/events and love it.
However, the thing I struggle with most is coming up with a topic. I find it incredibly hard to think of something I believe people will find interesting.
However, I expect this is simply down to lacking industry experience and not having spent extensive time working with any particular language/tool.
Its the dad's with fragile masculinity and out-dated opinions that would stop them going or teach them that those activities are 'girly'.