Not sure if that will help in this particular case, but that looks super neat anyway. I have been planning to build a custom modular synthesizer so I’ll try that out anyway. (Thankfully, it’s Kicad integration is free. Yay!)
Not sure if that will help in this particular case, but that looks super neat anyway. I have been planning to build a custom modular synthesizer so I’ll try that out anyway. (Thankfully, it’s Kicad integration is free. Yay!)
You were allowed to skip every Kazon episode except the one where they try to reverse engineer a replicator. (That might help on the next rewatch.)
My guess is that you are visualizing the event horizon as a gradient when it should be viewed as a hard-line barrier.
As anything approaches the event horizon, it still has a chance to escape. Once an object crosses that line, it’s game over: All arrows point in.
Now, I have also heard that of you wait long enough for the black hole to completely evaporate and are able to collect every bit of the black hole as it does, you should be able to reassemble the data you desire. It would probably take a supercomputer more massive than the original black hole, but it’s worth a shot. As a bonus, I believe you have to solve for an information duplication paradox that is tucked in there somewhere as well.
https://theonion.com/heres-why-i-decided-to-buy-infowars/
https://www.nbcnews.com/news/us-news/onion-wins-alex-jones-infowars-bankruptcy-auction-rcna179936
OMG, that is awesome! They have a limited amount of time to capitalize on that before all the Infowars drones catch on.
B. No illegal content.
While this particular community probably would not have an issue with “illegal content”, it still remains an extremely vague depending on where in the world you live. Are we talking about international law or laws in some random community in Texas?
If it’s useful to you, that is great.
Will rustc not just overwrite the old binary? If you are just doing a cleanup task, that’s cool. If nuking the last binary is important, then just do it first:
rm ./code; rustc ./code.rs -o ./code; ./code -mah args
I admire the willingness to share your work, but this is easier to do with a disposable one-liner at the prompt that you can repeat with an up arrow and a carriage return, if needed.
Sure, this script would be perfect for something like a cron job, but that would raise quite a few more questions as to why you would complie on a fixed schedule.
I can think of a few edge-cases where this script would be useful, but it just seems like it adds extra steps where extra steps might not be needed.
A hypothesis is absolutely fair game. I am not going to spend the time to prove it right or wrong in this case, but it’s still 100% legit in my book.
(Just don’t go telling your child spawn that space pot… err… space teapots are definitely the reason that time travel could be possible.)
I hate myths, even ones with good intentions. Things like “Santa” are just teaching kids to be disappointed and that their parents are full of shit.
As a side comment, what in the actual fuck is the tooth fairy?
None of this stuff makes any sense to me, whatsoever.
When I see my Dr. or when I talk to other engineers?
Any in many ways, that is the way engineers should speak to other engineers when analyzing a problem.
If two or more people can actually share a common goal of finding the best solution, everyone involved should be making sure that no time is wasted chasing poor solutions. This not only takes the ability to be direct to someone else, but it also requires that you can parse what others are telling you.
If someone makes something personal or takes something personal, they need a break. Go take a short walk or something. (Linus is a different sort of creature though. I get it.)
TBH, this is part of the reason I chose my doctor (GP). She is extremely direct when problem solving and has no problems theory-crafting out loud. Sure, we are social to a degree, but we share many of the same professional mannerisms. (We had a short discussion on that topic the other day, actually. I just made her job easier because I give zero fucks about being judged for any of my personal health issues.)
I watched through Day of Honor a couple of times today, but it was kinda choppy for me since I had to work.
I just want to clarify “give herself up” in that you mean she is willing to become part of the Voyager “collective” and puts aside her need to return to the Borg?
If my above assumption is correct, then yes. She is growing exponentially personality wise, but there are significant challenges in doing so.
Personally, I have been around engineers my entire life. Some people I know could rattle on for hours over something like p vs np even if they just learned about it a few hours ago. Put that same person in a complex social environment and they are absolutely clueless. It’s similar to Seven.
Assuming I didn’t know anything about her timeline after Day of Honor, my guess would have been it would take years for her to learn how to operate in a complex structure like we are accustomed to. Janeway seems bright enough to understand that as well. So yeah, it would be a very long time before she could make the kinds of decisions we take for granted and Janeway would have to do that for her like a parent.
Fast forward a bit to Picard, you can see how long it took for her character to develop into something that didn’t resemble a robot. (I am willfully excluding some later episodes of Voyager that were kind of odd, btw.)
Standby. I remember the episode but not with enough detail to discuss.(I’ll get it rewatched now.)
(New reply)
Really? That was your takeaway? ROFL!
It was totally fine. Borg implants or not, she was still human. She also didn’t have a choice about becoming Borg at such a young age. When her connection was cut with the collective, she basically became a child again making her Janeway’s responsibility. (That was close to Janeway’s logic I believe, and I agree with it. It was a human decision for another human who was incapable of making decisions.)
The biggest thing is that Seven has already signed a contract with UPN, so she was kinda stuck for a few episodes anyway. Janeway knew this, so after thinking about it over a 50 gallon drum of coffee and a few packs of menthol Kools, she decided to just run with it and make it dramatic. (The Borg attorneys failed to overturn the terms of the contract even after several weeks of absolutely phenomenal work.)
Voyager had it worse than Enterprise-D in general, but I am struggling to define “natural disasters” in this case. I’ll need help with this as I am not an Enterprise-D expert, but I think I can explain more about what I think is proper context from Voyager.
Strange aliens that invade the ship are just aliens doing what they do. It’s natural, but technically not a disaster.
Voyager getting pulled into the delta quadrant was an act of an entity and not really a disaster in the whole scheme of things. It was really bad, but limited in scope.
I almost classified a planet being destroyed by a dangerous power source explosion a natural disaster, but it’s not. It’s humanoids doing stupid humanoid things.
Voyager does have “Shattered”, that seems natural and a disaster, but it’s limited to just Voyager.
“Year of Hell” is so close, because time itself is keeping the imperium in a never ending cycle of wiping out entire civilizations, but doesn’t make the cut because it was still the work of one crew and the “disasters” technically never happened.
“Friendship One” may be in the running because a civilization was “gifted” with matter/antimatter tech before it was ready. It was a mistake of pure chance that kicked off a path to the destruction of a society.
(Enterprise-D had a few episodes where they were saving planets from actual natural disasters though. As mundane as that sounds, some of those may come out on top by definition.)
Edit: To completely destroy my own attempt to set content, “The Omega Directive” may be it as the Omega particle was able to create subspace ruptures. It’s perfectly and evenly tied with Enterprise’s “Force of Nature” where warp drives were destroying the fabric of subspace itself. In that context, both win. Unintentional and unexpected natural consequences of one force of nature acting on another. (I just completed wrecked my own previous arguments, I know. Just having too much fun with this one, s’all.)
Radio telescopes. While I don’t know the complete process of how an image is created, it’s likely a composite of hundreds of thousands of points where radio wave strength was measured.
A very basic explanation is that each radio antenna likely takes a reading of some kind for each equivalent pixel in the resulting image. Over time, you can build an image.
Again, I don’t know the full details of how the full image is recreated. It seems super complex reassembling millions of data points from antennas that are located on a rotating earth that is also rotating around a sun. The position of the earth probably has a huge impact on radio signal strength at any given time.
It would explain the poor memory I get when I smoke. You can’t remember something that hasn’t happened yet, so it naturally increases your ability to remember more. (Taps forehead…)
It’s a markup language(ish) but it’s not a programming language. XML would be closer to programming, IMHO, since you could have simple things like recursion. That example is even pushing what I would consider “programming”, but anyone can feel free to disagree.
SQL is in the same category for me. It’s a query language and can get super complex, perform some basic logic, but you can’t exactly write “snake” in it. Sure, you could use cmdshell or something else to do something more complex, but that would no longer be SQL.
My simplistic expectation of an actual programming language would be that you can automate an entire platform at the OS level (or lower) instead of automating functions contained within a service or application. (JVMs and other languages that are “containerized” are weird outliers, by my definition.)
I am not trying to step on anyone’s toes here. I just never have really thought about what I personally consider a programming language to be.
Not really surprising as we had recently evolved to stand on two legs and probably lacked the brain power to hunt effectively. We only started using fire sometime during the following two million years as a we transitioned into “modern” humans. Fire was likely a huge motivator to begin consuming meat once the maillard reaction was “discovered”. The last ice age probably kicked out hunting skills into high gear due to sparse vegetation and the need to consume more fats and proteins.